Email Inboxes
Create an Inbox, choose a Workflow or human reply, and see an Action that sends email. Read the transcript
An Email Inbox gives your workspace an address for receiving and sending email. You can reply yourself or route new threads to an Agent running a Workflow.
Create an inbox
- Open Connections → Inboxes and select New Inbox.
- Enter a name and the Address. The address starts from the name; change it if you want. Use lowercase letters, numbers, and hyphens. The rest of the address is fixed by the domain.
- Choose the platform domain or a verified organization domain. For your own domain, complete Domains first.
- Choose Who answers: AI with a Workflow, a human, or Custom routing.
- Select Create Inbox and copy the address shown in the inbox.
Platform addresses include the workspace slug, such as support_example@gravityrail.net. Custom-domain addresses use the address you typed, such as support@example.com.

Off discards unknown-sender mail without anyone reading it. On retains it for staff review; it still does not go to the AI.
Choose whether to retain unknown mail separately from who answers Member mail.
View full size ↗The first label starts open. Hover or focus to explore; click or tap to pin.
Decide who answers
Open the inbox's Settings and edit its Email Routing Rules. When a Bundle from the Library answers on this inbox, its rules show here read-only: install another version of the Bundle, or detach it, to change them. To have the Bundle answer on another inbox instead, use Change under Routing in the installed Bundle's settings.
- Add a rule for the schedule and audience you want to handle.
- Choose AI with a Workflow, a human, This inbox's owner, or an auto-reply.
- Put specific rules before broader rules.
- Use Test to inspect saved-rule matching, then send a real test email to check the destination and reply. Test itself does not send an email.
Routing applies to new threads. Replies remain in the existing Chat.
Set an Owner if a Member or Agent should answer when no rule does. Rules that choose This inbox's owner also use that owner. Before clearing the owner, remove those rules or change them in the same save.
For a human-only inbox, choose a human answer rule or a human owner without an AI rule.
A human answer rule rings the person while they are online. If nobody accepts, the email is not lost: when no later rule applies, it opens a paused Chat assigned to that person, and it appears in Needs response in Messaging.
Mail from unknown senders
Use Store unknown-sender email to keep mail from addresses that are not Members so your team can read and reply. This switch does not allow AI to read or answer that mail. When it is off, unknown-sender mail is discarded.
Stop automatic replies
Turn off Auto-Reply if the assistant should process incoming Member mail without automatically sending a response. This does not turn the inbox into a human-only inbox; use routing for that.
Read and reply
- Open the inbox and select an email row. Use the row menu to mark it read or unread. A Not processed tag marks mail the AI did not read.
- Select Reply and write your response.
- Use Preview to check the message, footer, and quoted original.
- Select Send.
The reply dialog shows who it goes to and the subject; only the message is editable. Closing it with text asks before discarding. The reply is sent from the inbox address. If a Workflow handled the email, open its linked Chat to review or continue that work.
To redirect replies to a fixed address, open Settings → Sender rules → Recipient and choose Alternate email address. Check this setting before sending a test reply.
Insert an image
- In Compose or Reply, select Image.
- Upload an image, choose a workspace file, or enter an external image URL.
- For a workspace file, choose Embed to include it in the email or Link to load it from its public URL. Add alt text and insert the image.
Linking a workspace image requires that file to already be public and shareable. Use the file's Share dialog if you intend to change access; the email editor does not change sharing for you.
| Image limit | Maximum |
|---|---|
| Workspace image references, embedded or linked | 20 per email |
| One embedded image | 2 MB |
| All embedded images together | 6 MB |
Preview does not load externally hosted images, and recipient email clients may render the message differently. Send a test email to check the final appearance.
Edit HTML
Select Raw HTML when you need to edit the message markup directly. If the rich editor cannot represent that markup, switching back asks before simplifying it.
Set the footer
Open Settings → Sender rules and edit the inbox footer, then save. It replaces the workspace footer for mail sent from this inbox. Leave it empty to use the workspace footer again.
For workspace-wide wording, see Email defaults. For personalized wording, see Template Variables.
Attachments
Received attachments are virus-scanned and appear with the email. Documents are also saved as Files linked to the email's Chat, so the Agent can read them, including scanned PDFs through document text extraction. A blocked file, a file over 25 MB, or a small inline image such as a signature logo is skipped on its own; the email itself is still delivered.
An Agent using the Send Email ability can attach workspace Files. Those outgoing file attachments are limited to five files, 7 MB per file, and 7 MB combined. Embedded images have the separate limits above. For larger files, share a file link instead; see File Browser and File Editor.
Restrict incoming mail
Open Settings → Sender rules. These controls determine whether mail can reach the inbox; they do not select the answering Workflow.
Allow or deny senders
- Select Allow Rules or Deny Rules.
- Choose Use rules and add a sender-email or sender-IP condition.
- Enter the operator and value, add the rule, and save.
- Send test mail from an address you intend to allow and one you intend to block.
Email conditions support contains, equals, ends with, and regular expressions. IP conditions support an exact address or CIDR range. A list matches when any of its rules matches.
| Mode | Allow list | Deny list |
|---|---|---|
| All | Allow every sender | Deny every sender |
| None | Allow no sender | Deny no sender |
| Use rules | Require an allow-rule match | Reject a deny-rule match |
Mail must pass the allow setting and avoid the deny setting. Deny All blocks delivery even if the allow list accepts the sender.
Adjust sender rate limits
Select Rate Limiting to set per-minute and per-hour limits. Leave a custom limit empty to use the system setting for that window.
If a trusted sender needs an exception, add its exact email address or a domain pattern such as @example.com to the rate-limit allowlist. That exception bypasses rate limiting, not the inbox's allow/deny rules. Record a reason so your team can review the exception later, then save.
See reply and bounce rates
Open an inbox and select the Analytics tab to see how the email it sent is doing.
- Choose a Period: Last 7, 14, 30, or 90 days, or pick your own dates. The default is the last 30 days, and a period can be at most 90 days.
- Read the three numbers:
| Number | What it means |
|---|---|
| Sent | Emails this inbox sent in the period. Each email counts once, however many recipients it had. |
| Reply rate | The share of those emails that received a reply. Automatic replies count too. |
| Bounce rate | The share of tracked sends (emails with delivery tracking) that permanently failed to deliver. No bounce doesn't prove an email arrived, because delivery feedback can come late or not at all. |
Reply rate and Bounce rate show their counts beneath the rate, such as 12 of 234. Select the info icon next to a number to read its definition.
Keep these limits in mind:
- Earlier replies aren't included. Replies are counted from when Inbox Analytics was introduced, so older emails may show no reply even if someone answered.
- Unknown-sender replies need storage. If Store unknown-sender email is off, replies from addresses that are not Members are discarded and never counted.
- Changing the inbox address resets the counts. Emails sent from the inbox's old address no longer appear after its address changes, and replies to them are no longer counted.
- Bounce data can be partial. When some emails have no delivery tracking, the tab shows how many sends the bounce rate covers.
To see the tab, you need the View analytics and reports permission (analytics:read) and inboxes:read, plus admin access to that inbox: you own it, your role has inboxes:admin, or you were granted access to it. Without inbox admin access, the tab explains that you need it.
Check a missing email or reply
| Symptom | Check |
|---|---|
| Mail from an unfamiliar address is missing | Store unknown-sender email, allow/deny rules, and sender rate limits. |
| Mail arrives but no AI answers | The sender is a Member, an Email Routing Rule selects AI and a Workflow, and Auto-Reply is on. |
| A patient's reply gets no AI answer | The Member's email must be the address they sent from, and their email provider must authenticate the mail (DMARC). Check the Member's email, or use Add sender as member. |
| A reply reaches an unexpected address | Recipient in the inbox's Sender rules settings. |
| The wrong footer appears | The inbox footer overrides the workspace footer. |
Permissions
Inboxes no longer have per-role access checklists. Role scopes apply Workspace-wide: inboxes:read lists Inboxes and allows using one as a receiving destination; inboxes:write allows creating an Inbox and authorizing automated sending from its address; inboxes:admin allows managing Inboxes and reading their messages.
Ownership and explicit individual grants still provide Inbox-specific access. In the app, reading stored mail also requires inboxes:read, editing an Inbox requires inboxes:write, and Compose, Send, and Reply require inboxes:admin. Being the Inbox owner does not replace these screen and action requirements.
A Send Email ability or Event Rule checks the configuring Member's permission to send from the inbox when it is saved. When it runs, it sends with that authority; Members served by the automation do not need inboxes:write.
For role setup, see Member Roles.
Related
An inbox with no address yet
An inbox can exist before it has an address, for example one a Bundle created for a practice whose email will be on its own domain. The list and the inbox's page show No address yet. Until it has an address, it does not receive email and nothing can send from it: an Action, a Workflow or a Journey step that uses it fails instead of sending, a new email chat cannot use it, and a Journey with a switched-on step that emails from it cannot be published.
To give it an address, open the inbox and select Give it an address. If your organization has verified email domains, choose one of them or the Gravity Rail domain; otherwise the address is on the Gravity Rail domain. The address is built from the inbox's address prefix in Settings, so change the prefix first if you want a different one. Everything that uses the inbox starts sending from the new address. Saving other settings does not give it an address. You need permission to edit inboxes.
Archive an inbox
Archiving retires an address without deleting it. The inbox leaves the Active list and appears under Archived in the page-header view switch. It stops receiving mail, cannot send, and its settings become read-only — but every email, attachment and thread it holds stays readable. The address stays reserved, so no new inbox can take it. You need inboxes:admin.
To archive, open the inbox's Settings and select Archive in the Archive card, or select Archive from the inbox row menu. If a Workflow uses the inbox as its default, or an Action or Routine sends from it, the confirm dialog lists it and Archive stays disabled until you point that sender somewhere else.
Archiving cannot be undone.
Delete an inbox
Open the inbox's Settings and select Delete inbox at the bottom. It deletes the inbox and all its emails and cannot be undone. You need inboxes:admin. Deleting is also how an archived inbox's address is freed.