Inbox overview
Connect Gmail, Outlook, or IMAP mailboxes, read and compose threads, and automate with templates and notification rules.
Inbox is Pointerly’s unified mailbox for brand and marketplace email: connect Gmail or Outlook (OAuth) or other providers via IMAP/SMTP, read folders both ways, compose replies, manage signatures, and automate with templates and notification rules (subject/from/snippet variables).
What you'll do
- Open Dashboard → Inbox
- Connect a mailbox from Integrations if none is linked
- Browse threads, switch accounts/folders, and Compose
- Configure Templates and Rules from the workflow panel (
?panel=templates/rules)
Before you start
- You can access Integrations to connect a mailbox
- For Gmail/Outlook: use the account that receives affiliate reports and brand replies
- For IMAP: have host, port, and SMTP credentials ready
- Managed connectors may be enabled for your environment—follow the on-page connect flow
Image placeholder — add `images/overview-cover.png` under this category
Steps
1. Open Inbox and connect a mailbox
- Go to Dashboard → Inbox.
- If no mailbox is connected, use Connect mailbox (routes you through Integrations).
- Prefer Gmail or Outlook OAuth for two-way folder sync; use IMAP for other providers and configure SMTP so you can send.
- Return to Inbox and select the active account when multiple are connected.
- Use Reconnect / re-authorize if sync tokens expire.
Image placeholder — add `images/overview-step-01.png` under this category
2. Read and organize threads
- Browse the thread list (All / per-mailbox filters when available).
- Open a thread in the reading pane; load more pages as Gmail/Outlook cursors allow.
- Sync folders so labels/folders stay aligned with the provider.
- Use search and folder navigation provided in the Inbox chrome to find reports and brand threads quickly.
Image placeholder — add `images/overview-step-02.png` under this category
3. Compose and reply
- Click Compose (requires an active connected account).
- Write in the compose dock; open multiple drafts if needed (extra drafts stack; overflow appears as “+N drafts”).
- Insert signatures managed in Inbox settings / signatures section.
- Use the rich text editor for formatting when available.
- Send; confirm the message appears in the Sent folder after provider sync.
Image placeholder — add `images/overview-step-03.png` under this category
4. Templates and notification rules
- Open the workflow panel — Templates or Rules (URL
?panel=templatesor?panel=rules). - Create reusable reply templates for common brand or report acknowledgements.
- Create rules that match inbound conditions and run actions (notify, label, forward-style workflows depending on configuration).
- In rule action text, insert variables:
{{subject}}— message subject{{from}}— sender{{snippet}}— preview text
- Enable the rule and watch trigger count rise as matching mail arrives.
- Gmail system mail that should be skipped for rules follows product skip logic—prefer rules on human/brand senders.
Image placeholder — add `images/overview-step-04.png` under this category
Tips
- Keep Amazon Associates and brand negotiation mail in the same connected inbox so reports and collabs stay searchable together.
- Start with one OAuth mailbox before adding IMAP aliases.
- Use templates for rate cards and “report received” replies to cut response time.
- Pair high-priority rules with Notifications so you catch matches outside the Inbox tab.
- Re-run OAuth when folder sync stalls after password or security changes at Google/Microsoft.
Troubleshooting
| Symptom | Likely cause | What to try |
|---|---|---|
| Connect mailbox empty state | No integration linked | Integrations → connect Gmail/Outlook/IMAP |
| Compose disabled | No active account selected | Select a connected mailbox |
| IMAP receives but cannot send | SMTP not configured | Complete SMTP settings for that integration |
| Sync stale / auth errors | Expired OAuth token | Reconnect / re-authorize the mailbox |
| Rule never fires | Conditions too strict or skipped system mail | Broaden matchers; test with a real brand email |
| Variables not replaced | Typo in token | Use {{subject}}, {{from}}, {{snippet}} exactly |