Communications Hub
How Muin's Communications Hub unifies email, SMS, and WhatsApp in one inbox with AI auto-responses, so your team answers every message from a single place.
28 questions
How does Muin send email out of the box?
By default, Muin sends donor receipts, payment alerts, and broadcast campaigns from `<your-tenant-slug>@falaah.ai` over Muin's managed AWS SES infrastructure. No DNS setup is required: every tenant has a working sender from day one. Add your team's Reply-To address at **Settings** → **Communications** → **Channels** so donor replies route to a real inbox you watch.
Can I send from my own domain instead?
Yes. Run the optional 6-step branded sender wizard at **Settings** → **Communications** → **Set up branded sender**. It generates DKIM and MAIL FROM records; you add them at your DNS host; SES verifies (typically <15 min). After setup, receipts come from `support@your-domain.example` and replies route into the Muin comms hub. Every wizard step has a built-in **Get help →** link if a record won't verify.
What's the difference between the From address and Reply-To?
The From address is who the email looks like it's from. Reply-To is where replies go when a recipient hits Reply. With Muin's default sender, From is `<your-tenant-slug>@falaah.ai` and Reply-To is your team's inbox: donors see Muin's address but their replies land where you can see them. With a BYO branded sender, From and Reply-To both live on your own domain and replies route into the Muin comms hub.
My donor isn't receiving receipts. What should I check?
1. Confirm their address isn't on your tenant's suppression list at **Settings** → **Communications** → **Suppression**. 2. Check the audit log at **Admin** → **Communications** → **Audit** for the sent-email row: bounces and complaints will show the SES diagnostic. 3. If you're still stuck, click **My donor isn't receiving emails →** on the email channel card to open a tagged support ticket. Our ops team works the `email-deliverability` runbook within 1 business day.
How do I find a specific email Muin sent?
Open **Communications → Email Activity Log** and type in **Search emails**. It matches the subject line and the recipient's name and email address, so a parent's name, a child's name (a payment receipt's subject names the child) or an address all work. Narrow further with the email type filter, for example **Tuition Payment Received (paid in person)**, and a date range. Each row links to the person, the enrollment and the payment it belongs to, so you can go from the email straight to the record behind it.
Can I see emails my donors send to my regular inbox?
Not yet. Connecting your own Microsoft 365 or Google Workspace mailbox so its mail flows into the unified inbox is built but **not enabled**: it isn't available to any tenant today. Personal Gmail connect is unavailable too. What works now: donors who reply to mail Muin sent (receipts, campaigns, messages) come back into the comms hub automatically, and you can route an address like `info@` to Muin by pointing your email provider's inbound webhook at it. Ask us if you want that set up. Two limits to know for when mailbox connect does ship: it is **read-only** (Muin won't send from your address), and a message body is private to you and your organization's admins. Teammates with People access see the sender, date and subject on the person's timeline, never the body.
Is my email content stored anywhere?
Email metadata and audit-log entries (sender, recipient, subject, message-id) are stored 90 days for operational diagnostics. Email body content is stored in your tenant's database. Email bodies and call notes captured on a person's record are kept for as long as that person record exists, and are removed when the person is erased under a privacy (GDPR) request. Privacy controls: PII addresses are masked in operational logs (`mask_email`), and the platform never logs full message bodies.
Can I connect my Outlook account to Muin?
Not yet. Microsoft 365 mailbox sync is built but not yet available to organizations. What works today: BCC an email to your capture address and it lands on the Timeline of each person on it who is already in Muin (see [Email forwarding](/docs/platform/integrations/email-forwarding)). When mailbox sync opens, the [Microsoft 365 connection guide](/docs/platform/communications/connect-microsoft-365) covers the IT admin consent step.
Can I connect my Gmail to Muin?
Not as a mailbox sync yet. Google Workspace mailbox sync is not yet available to organizations, and it also waits on Google's verification of Muin's app. What works today: BCC an email to your capture address to log it to the person (see [Email forwarding](/docs/platform/integrations/email-forwarding)). For **personal `@gmail.com`**: Muin uses a privacy-first forwarding bridge, we never read your inbox, you set up a Gmail filter that forwards just the messages you want into Muin. See the [Workspace guide](/docs/platform/communications/connect-google-workspace) and the [personal Gmail guide](/docs/platform/communications/connect-personal-gmail).
What can Muin see when I connect my mailbox?
Microsoft 365 + Google Workspace: messages in the folders/labels you select (default: Inbox), plus your name and email. We never request access to calendar, contacts, files, Teams chats, Drive, or any other service: mailbox-only. Access is **read-only**: we do not request `Mail.Send` / `gmail.send`, because Muin never sends from your address. Mail synced from a connected mailbox keeps its body private to you and your organization's admins. Teammates with People access see the sender, date and subject on the person's timeline, never the body. Personal Gmail connect is currently unavailable (it existed only to send).
Can my colleagues see my mailbox messages?
No. Mailbox connections are per-user: each person connects their own account, and tokens are stored against that user only. Muin never copies one user's mail into another user's view. Your tenant admin can open an admin-only Connected Mailboxes overview, but it shows connection metadata (who connected, when, last sync), not message content. Messages from your connected mailbox stay yours.
What happens when I disconnect my mailbox?
Tokens are cleared immediately when you click **Disconnect** at **Settings** → **Communications** → **Connected mailboxes**. Sync stops on the next tick. Messages that were already synced into your comms hub remain by default: you can choose to delete them in the disconnect dialog if you'd like. For personal Gmail: we can't delete your Gmail filter for you (we never had access to it), go to Gmail's **Filters and Blocked Addresses** to remove it manually if you no longer want forwarding.
Is the OAuth process secure?
Yes. We use OAuth 2.0 with PKCE (Proof Key for Code Exchange) for both Microsoft and Google flows, that prevents authorization-code interception even on a hostile network. State tokens are single-use, bound to your session, and expire after 5 minutes. Refresh tokens are encrypted at rest with a dedicated application encryption key, and we never store a token in readable form. We never see your password: Microsoft and Google handle the sign-in directly. You can revoke Muin's access at any time from your provider's account-security settings.
Why does Google Workspace require admin trust?
Google Workspace lets organization admins decide which third-party apps can access their employees' Gmail. Until your Workspace admin trusts Muin once at the org level, every member of your team would see "unverified app" warnings during the OAuth flow. Trust is a one-time, ≤5-minute setup at admin.google.com: see the [Workspace admin guide](/docs/platform/communications/google-workspace-admin-setup). After trust, your whole team connects without warnings, and the admin can revoke trust any time to remove all Muin connections from your org at once.
Why doesn't personal Gmail show my inbox in Muin?
Personal Gmail connect is **currently unavailable**, so it doesn't show your inbox at all. The flow's only purpose was to send from your personal address, its inbound came from a Gmail forwarding filter you set up, never from inbox access, and sending from a connected mailbox isn't supported yet, so Muin no longer requests `gmail.send`. The design rationale still holds for when it returns: personal accounts often hold deeply personal mail (bank statements, medical records, family conversations), so the flow deliberately never asked for inbox-read access. If you want full inbox sync for a work account today, use the Workspace flow with your IT admin's approval.
How do I ask the people I'm messaging to sign up for something?
Attach a form to the broadcast. In the composer, open **Sign-up sheet**, choose a published form, and confirm **Attach and lock**. Three things happen when you confirm, and nothing happens before: 1. The form is switched to **invite-only**, so only the people in this broadcast can answer it. Any link you had already shared stops accepting new people, which is why the composer says so before it does it. 2. `{{invite_link}}` is added to your message. Each recipient gets their own private link, so you can see who answered and who has not. 3. Nothing is sent. The send is still your own separate click. If you remove the form afterwards, Muin offers to put the form's public access back the way it was. Links already sent stay valid either way. Every channel you send on needs the link: if you write a separate SMS or WhatsApp version, `{{invite_link}}` has to be in that version too, or Muin will refuse the send and tell you which channel is missing it.
Where do I see who signed up after a broadcast?
Open the broadcast and look at the **Sign-up sheet** card: it shows invited, opened and responded, plus how full each slot is. Those counts are **the form's totals**, across every broadcast that has ever sent it, not just this one: Muin does not break invite counts down per broadcast. Open the form itself for the individual responses. To chase the people who have not answered, use **Remind non-responders**: it opens a new broadcast aimed only at the people this broadcast went to who have not answered, carrying the same form and therefore the same links. People invited by a test send or another broadcast of the same form are not included.
Can I stop a message before it goes out?
Yes, as long as it is still queued. Open **Communications** → **Scheduled Messages**, find the row, and click **Stop this message**. You will be asked to confirm, and the row moves to **Stopped**. Two things to know. Muin checks the queue **every five minutes**, so a message scheduled for 10:00 goes out between 10:00 and 10:05, you have until that pass to stop it. And a message that already reads **Sent**, **Skipped** or **Failed** has settled and cannot be stopped. Stopping needs edit access to communications; with view-only access the button is not offered.
A scheduled message says Skipped. What does that mean?
**Skipped** means Muin chose not to send it. The usual reasons are that the person has opted out of marketing and announcement emails, or their address is suppressed after a hard bounce, or the notice itself was switched off between the time it was queued and the time it was due. **Failed** is different, the send was attempted and rejected. Open the row and read **Last error**. To see a person's contact status and whether their address is bouncing, open their record in the directory.
How do I personalize a message template?
Write the variable in double curly braces where you want the value to appear, for example `Thank you, {{customer_name}}`. The editor reads your subject and body as you type and lists every variable it finds, so you can see what the template expects before you switch it on. The commonly used ones are `customer_name`, `company_name` and `date`. There is no fixed list you must choose from, so keep to names you know you hold on the person's record, a variable Muin cannot fill is left unsubstituted in the sent message. Always preview a template before you activate it.
The Message Templates page says "Failed to load templates". Why?
Almost always a permission problem rather than an outage. The templates screen opens for a role with broadcast access, but every request it makes needs the **communications automation** permission, so the page paints and the list fails. Ask your owner or admin to grant communications automation access to your role. The same permission covers routing rules, SLA policies and automation sequences.
Can I edit an automation sequence that people are already in?
Yes, and the change takes effect immediately. There is no draft state, saving a step changes what everyone who has not yet reached that step will receive. Anyone who has already passed the step does not get it again. If you need the old wording preserved for people mid-flight, build a new sequence and switch the old one off instead of editing it. Switching **Enabled** off stops new sends but does not remove existing enrollments, so stop those individually if you need to. To take one person out, open the sequence's **Enrollments** tab. **Pause** holds their next send only; **Stop** removes them permanently and re-enrolling them later starts at step 1.
What is the Demo Inbox and why can't I see it?
The Demo Inbox is a mail-client view of every email a **demo** workspace sends, sign-in codes, receipts, messages, exactly as recipients receive them. It exists so you can demonstrate or test a flow end to end without a real mailbox. It appears in the Communications menu on demo workspaces only. On a real workspace it is not available, and the API refuses the request: customer mail is never readable this way.
Communications Analytics says "Unable to load analytics". What should I check?
First try **Retry**, the panels load independently and a single slow request can fail the card. If it keeps failing, it is a permission grain: the Analytics screen opens for a role with broadcast access, but its data needs the **communications automation** permission. Ask your owner or admin to grant communications automation access. While you are there, note that **Customer Satisfaction** reading **Not available** is not an error, it means no satisfaction responses were collected in the date range you picked.
Can a supporter stop fundraising appeals but keep the newsletter?
Yes. People choose which kinds of email they get, one kind at a time: **Newsletter**, **Fundraising appeals**, **Event invitations**, **Impact updates** and others. Receipts and other mandatory messages are never affected. When you write a broadcast or a message series step, you answer **What kind of email is this?** The answer decides which opt-out applies, and the unsubscribe link in that email's footer turns off only that kind. **Settings → Communication & AI → Customer Emails** shows, on each row, which opt-out covers that email. **Campaign Launch Announcement** and **Campaign Milestone** are fundraising appeals and are off by default. Turned on, they only save a draft on the Broadcasts page for your team to review and send.
Can Muin thank donors on the anniversary of their first gift?
Yes, once you switch it on. The **Donor Anniversary Thank-You** is off for every organization until an admin turns it on in **Settings → Communication & AI → Customer Emails → Giving → Donor Anniversary Thank-You**. With it on, the **Donor Anniversary Trigger** agent finds donors whose first gift has its anniversary today and queues a thank-you for 9:00 AM in your organization's time zone. Each one waits for a person to approve it, unless someone has set a standing rule that lets overnight agents queue donor messages. You can read or stop every queued thank-you in **Communications → Scheduled Messages** before it sends. While it is off, the agent queues nothing and its run says so, naming the switch to turn on.
How do I log an email to a person?
BCC your organization's capture address on the email when you send it. Forwarding an email to it later does not log it. The address is your slug plus `+log`, for example `your-org+log@inbound.falaah.ai`. Copy it from **Settings → Email Forwarding** or from the setup steps on a person's empty **Timeline**. The email lands on the Timeline of every person on it who is already in Muin. Only mail from your staff address is accepted, and no one is created from mail.
Who can see an email logged to a person?
Anyone with People access sees who the email was from and to, when it was sent, and its subject. The body is visible only to the staff member it was captured from and to your organization's owners and admins. This applies to BCC'd mail and to mail synced from a connected mailbox, including in inbox search and AI drafts.
Other FAQ Categories
Didn't find your answer?
Our support team is happy to help with any questions.
Contact Support