SquidSupport
Product reference / Settings

Email

In the app: Settings → Email

Needs the 'View Email Config' permission.

Connect a store's support email address to Squid, so customer email arrives as tickets and replies leave from your own address. Everything on this page belongs to the store chosen at the top: its mailboxes, its domains, its sender name and its signature. Other stores have their own.

How email integration works

The store picker at the top chooses the store. "Add store" creates a new one, and "Rename or delete stores" goes to Settings → Stores.

Email reaches Squid by forwarding. Your support address stays where it is, at your own email provider. You add a rule there that forwards its mail to an address Squid gives you. Replies are sent by Squid in the name of your own address, which needs a few DNS records on your domain so that mail providers trust them.

"How email integration works", behind the (i) button next to the title, lists the four steps for an address on your own domain: add your domain, add your DNS records, forward your mail, start receiving customer email.

Seeing this page needs the 'View Email Config' permission. Adding, changing, verifying and removing email configuration needs 'Edit Email Config'. Creating a store with "Add store" needs 'Edit Brands'.

A warning "No emails received at …" appears when a mailbox marked verified, or an old mailbox still receiving during a domain change, has received nothing for more than 24 hours. This can include a receive-only mailbox with no DNS records of its own. It names the receiving address's domain, counts from the last email that arrived at that mailbox and says how many hours ago that was. It can mean the forwarding rule at your provider stopped working; "Check forwarding" jumps to that mailbox when its card is on the page. A quiet weekend can trigger it too, for a mailbox that normally gets little mail. A mailbox that has never received any email does not get this warning, and neither does one still awaiting DNS verification. The warning is worked out when you open the page.

Email we received but could not route

This panel lists email that reached Squid for this store but could not become a ticket: mail for an address that is not set up as a mailbox here ("Address not configured"), and mail for a domain whose DNS records are not verified yet ("Domain still verifying — held until setup finishes"). It is grouped by address, with the number of waiting emails, when the last one arrived and up to two senders. Such mail is held, not turned into tickets. "View" shows the held emails of one address. When there is none, the panel reads "No unrouted mail".

The button "Add to" followed by the store's name opens "Add mailbox to store". "Register mailbox" there registers the address as a mailbox of the store, so future mail can become tickets once any required domain setup is finished. "Also import the … captured email" is ticked to begin with: Squid then queues the held emails for import. Emails it can route appear in the inbox shortly after, without their attachments (the ticket says so). An import that cannot route returns to the held-mail list. Unticked, the held emails stay in this list.

What the new mailbox can do depends on its domain. On a domain the store has already set up and verified, it shares that domain's DNS records and can send replies. On a domain the store has not configured, a newly registered mailbox only receives: replies cannot be sent from it, and it has no DNS records to add. If the address already exists with unfinished DNS setup, registration keeps that setup pending. Finish DNS verification before importing its held mail. An address on Squid's own mail domain cannot be added this way.

A single held email can be discarded with the bin button next to it, at once and without a confirmation. Held mail is not released by itself when a domain's setup is finished; import it with the "Add to" button. A held email that is not imported or discarded leaves this list 30 days after it arrived, and held, imported and discarded emails are deleted from this store 90 days after they arrived. Tickets made from them stay.

Set Up Email Channel

For a store without a mailbox, the page shows "Set Up Email Channel". Stores that are offered a Squid address first choose between "Forward to a Squid address" and "Receive on my own domain"; the Squid address is explained in its own section. For a store that already has a Squid address the card is titled "Add a mailbox on your own domain", and for a store that already has a domain, "Add a mailbox on a new domain".

Receiving on your own domain starts with "Domain Details":

  • "Your Domain": your company's main domain, such as yourbrand.com. You can paste a full web address; Squid takes the domain out of it.
  • "Public Support Email (customers see this)": the part before the @ of the address customers write to. It starts as "support".
  • "Support Subdomain (for receiving)": the subdomain on which Squid receives the forwarded mail. It starts as "helpdesk". Before forwarding is verified, replies use the receiving address as their Reply-To address, so customers can see it.

"Continue to Review", which appears once you have typed a domain, shows the DNS records you are going to need and what happens next. "Set Up Email Domain" creates the mailbox; "Back" returns to the fields. Nothing is created before that button.

A second domain needs its own DNS records. For another address on a domain you already have, use "Add a mailbox" instead.

DNS records

Each domain shows its DNS records under "Setup Progress", step 2. You add them at your DNS provider, not in Squid. Each record has a "Host / Name" and a "Value" with copy buttons, and a line saying what it is for:

  • records that sign your outgoing mail (DKIM);
  • a return path for bounces. It also covers SPF, so there is no SPF record to add; leave an SPF record you already have as it is;
  • a record that delivers mail for the receiving subdomain to Squid;
  • a record that proves you own the domain;
  • a DMARC record, marked "Recommended". It is optional and applies to your whole domain. If your domain already has a DMARC record, keep yours.

"Verify DNS Records" makes Squid look the records up. Each record then shows "Found", "Not found yet" or "Wrong value" (with the value that was found); before the first check they read "Not added yet". DNS changes usually show within minutes but can take up to 48 hours, so "Not found yet" right after adding a record is normal. The time of the last check is shown.

Squid also checks records that are not verified yet on its own, so you do not have to come back to click the button: several times an hour during the first day after the domain was added, then about every 6 hours, for up to 14 days.

Once the records are verified, replies can be sent from the address. Receiving also needs forwarding, the next step.

Mailboxes on the same domain share one set of records. A receive-only mailbox that was added from held mail on a domain the store has not set up has no records and no "Verify DNS Records" button.

Set Up Email Forwarding

Step 3 is done at your email provider, not in Squid: add a rule that forwards mail for your support address to the receiving address the step shows. The step has instructions per provider on three tabs, with both addresses filled in. "Google Workspace" opens first; for an address listed under a Squid address, the tab of the provider that address's domain uses opens first when Squid can tell.

  • "Google Workspace": in Gmail's settings, under forwarding, add the receiving address as a forwarding address. Google sends a confirmation email, which appears on this page; click its link to switch forwarding on. If your support address is an alias on another mailbox, leave general forwarding off and make a Gmail filter that forwards only mail addressed to the support address.
  • "Microsoft 365": in the Exchange Admin Center, make a mail flow rule with the condition that the recipient is your support address and the action "Redirect the message to" the receiving address. Use this rule for a mailbox of its own and for an alias; avoid forwarding a whole mailbox that also gets other mail. For a Squid address the tab warns that Microsoft 365 blocks forwarding to outside addresses until your Microsoft 365 admin allows it.
  • "Other Providers": make a forwarding rule at your provider from the support address to the receiving address. For an alias, use a rule or filter for that recipient only.

Google sends a confirmation email to the forwarding address before it starts forwarding. Squid catches Google's confirmation email and shows it here under "Forwarding confirmation received", with the link or code to confirm, so you do not have to look for it in an inbox. While forwarding is not proved yet, the page checks for it every 10 seconds; "Check now" checks at once. Confirmation emails of other providers are not shown this way, so if nothing appears, that is normal for them.

"Test Forwarding" proves the whole route. "Send Test Email" sends a message to your support address and waits for it to come back through the forwarding rule, checking every 5 seconds for up to 2 minutes. It is available once the DNS records are verified.

  • Success: "Forwarding verified!" The mailbox's "Receiving" line then says it works. A real customer email that is addressed to your support address and arrives through the forwarding rule proves forwarding in the same way, without a test.
  • Failure: the step says where the test stopped: the address refused it, it was never delivered, it was delivered but not forwarded to Squid (the forwarding rule is the missing step), or your mail server is still holding it. If there is no delivery report, the page says the test has not arrived and gives possible causes rather than a confirmed diagnosis.

"Recent emails at …" lists the latest mail that arrived at the receiving address, which helps to see whether forwarding works.

Squid address

Stores that are offered it can skip the receiving subdomain and forward to a Squid address instead.

Who gets a Squid address. A store is offered one when all of this is true:

  • the store was created after Squid addresses were introduced. An older store does not see the choice and receives on its own domain;
  • Squid's receiving service for these addresses is working at that moment. When it is not, the page says Squid addresses cannot be issued right now; try again later;
  • for an organization on a trial: no other store of the organization has a Squid address yet. A trial includes one Squid address for the whole organization; a paid plan gives every store its own.

When a store cannot get one, the page says which of these applies. A store that already has a Squid address keeps it.

"Which addresses do your customers email?": list every address customers write to, such as support@ and returns@ on your domain, up to 20 per store. Each listed address has to be forwarded to the store's Squid address. Within your organization an address can be listed on one store only; the page names the store that already has it. An address on Squid's own mail domain cannot be listed.

"Your Squid address" is shown with a "Copy address" button. It only receives: no reply is ever sent from it.

"Forward each address and test it": for each listed address, set up forwarding at your provider and send a test. A line per address says whether forwarding works. A test to the same listed address can be sent once a minute, and an organization can send 30 such tests an hour. If the mail arrives as a new message instead of a redirected one, the page asks you to change the rule at your provider to "Redirect".

"Replies": to send replies from a listed address on your own domain, add the DNS records the section shows and verify them. Nothing about your incoming mail changes. Until an address can send, either the store sends replies from another verified address it has, or no reply can be sent and what the AI writes waits as a draft. "Do this later" hides the records for now.

Addresses at Gmail, Outlook.com and other free email services can be listed and will receive, but replies cannot be sent from them.

"Stop listing it" removes an address from the list. Mail it still forwards keeps arriving through the Squid address. The removed address is no longer offered as a sending choice. Existing tickets can still attempt to reply from a removed sending address when the store has no live address that can send.

Mailboxes

The page groups your mailboxes by domain, for example "3 mailboxes on 1 domain". Each mailbox card shows the address and two status lines:

  • "Receiving": whether customer mail to the address arrives in Squid, or what is still missing (DNS not verified, or forwarding not proved).
  • "Sending": whether replies are sent from the address, or why not.

A store can have one mailbox with the "Primary" badge. The first mailbox added on its own domain becomes primary if the store has no live primary already. A mailbox registered from held mail is not automatically made primary. A reply to a ticket is sent from the mailbox the ticket arrived at, unless the person replying picks another sending address. The primary mailbox is used when there is no such mailbox to follow or that mailbox cannot send, for example for a new outbound email or a ticket that did not start as an email. "Make … primary" moves the badge; it is not offered on a mailbox that only receives.

"Add a mailbox" adds another address on a domain you already set up: type the part before the @ under "Address", pick the "Domain", and click "Add mailbox". It uses the domain's existing DNS records. It still has to be forwarded at your provider.

"Remove …" deletes a mailbox after you type its address to confirm. The removed mailbox no longer routes new mail. What happens to mail still forwarded depends on the other configured addresses and receiving setup that remain. Tickets that came in through it stay in the inbox. Replies to them then leave from another mailbox of the store that can send: the same address if you add it again, otherwise a primary address that can send, or another sending address if the primary cannot. If there is no live sending address, existing tickets can still attempt to send from a removed address, even though its sending setup may have been removed. Removing the last mailbox on a receiving domain also attempts to remove that receiving setup. Its sending setup is removed only when no other live mailbox uses it. Setting up a domain again can require new DNS records. An address hosted by Squid has no "Remove" button.

AI handling

Each mailbox, and each listed address under the Squid address, has an "AI handling" choice for the tickets that arrive at it. A receive-only mailbox that was added from held mail does not have it.

  • "Answer": the AI handles this mail with the store's AI settings, including sending by itself if the store has that on. This is the default.
  • "Draft only": the AI still writes a reply, but it always waits as a draft for a person to approve, also when the store sends automatically. The AI cannot do refunds, cancellations or other actions for mail in this mode, and it skips its automatic follow-ups on these tickets, except the ones started by a supplier's update or by the expiry of a supplier's promised update. Those exceptions still wait as drafts.
  • "Never touch": mail to this address is never given to the AI, also not by an automation rule that sends tickets to the AI. It goes straight to your team.

The choice is saved as soon as you pick it and applies to AI runs from then on. Automation rules and SLA policies can also be limited to one mailbox; look for "Received at mailbox" in automation rules and "Mailbox" in SLA policies.

Change Domain

"Change Domain" moves a mailbox to a new domain without losing mail in between. The button is on mailboxes on your own domain whose DNS records and forwarding are both verified. Whichever mailbox you click it on, the move uses the store's verified primary mailbox on its own domain. If there is no eligible primary, it uses the oldest verified sending mailbox on the store's own domain instead. The new address keeps the same part before the @. A store can have one such move at a time. It is a wizard:

  1. "Enter New Domain": the new domain, its receiving subdomain, and for how many days the old domain keeps receiving after the switch (1 to 30, default 7).
  2. "Add DNS Records": add and verify the records of the new domain. The old domain stays active meanwhile.
  3. "Set Up & Test Forwarding": point your forwarding rule at the new receiving address and test it.
  4. "Activate New Domain": after you confirm, the new mailbox becomes the primary and the old one stops sending at once, so replies that would have left from the old address leave from the new one. The old domain keeps receiving for the number of days you chose and is then removed. Other mailboxes of the store are not changed.

"Cancel" during the wizard, after a confirmation, removes the new domain and leaves everything as it was. After activation the move cannot be cancelled.

Email Appearance

How emails from this store look to the customer. It applies to every mailbox of the store.

"From Name", the sender name, is the name customers see next to the address, on emails written by the AI and by your team alike. It starts as the store's name followed by "Support". You can type any fixed text, or insert the store-name variable with "Insert Variable", which is replaced with this store's name when an email is sent; while the name contains a variable, the line "Customers will see:" shows the result.

"Email Signature" is added under every reply and every new email sent from a ticket of this store. A new store starts with a closing line in the store's language followed by the agent-name variable. That variable is replaced with the store's AI agent name, also on replies your team writes; if no agent name is set, the store name is used. "Preview" shows the result, and "Suggestions" offers sign-offs in several languages.

Notes the section shows when they apply:

  • If the config set this store runs for email has its own custom sign-off turned on and contains text or an image, that sign-off replaces this signature on the store's emails, until it is turned off. An email written by the AI carries the sign-off of the config set that wrote it, which can be another one during an AI test.
  • If your saved signature does not contain the agent-name variable, a line says the AI agent name does not appear in your sign-off.
  • If no stored signature or config-set sign-off applies, AI-written emails sign off with the AI agent's name only when it differs from the store's name. Otherwise they have no sign-off. Replies your team writes have no automatic sign-off.
  • "AI replies sign off as" shows what AI-written emails currently end with when that differs from what you see in the editor.

"Save Email Appearance" saves the sender name and the signature. They apply when later emails are prepared for sending; emails already queued keep the appearance they were prepared with.