Help Scout Conversation Creation
Turn an in-app help request into a Help Scout conversation in the right mailbox.
What it adds
A submission path that opens a Help Scout conversation with the customer, mailbox, tags, and assignee already set correctly.
What your agent is told to do
5
What your agent is told to do
5-
1
Resolve the customer from the authenticated session and match on that address exactly. Do not create a customer from a free-text field the user can type, and do not read a matched customer's history back into the app.
-
2
Make the destination mailbox, tag set, and default assignee configurable per request type, and validate the chosen mailbox when the configuration is saved rather than discovering it is gone at submission time.
-
3
Preserve what the user actually wrote: line breaks, ordering, and any quoted error text. Send it in a form the provider renders faithfully instead of collapsing the whole message into one paragraph.
-
4
Carry a request identifier generated before the first attempt through every retry, and deliver through the app's existing background-job system so retry and backoff behaviour is the one the app already has.
-
5
If Zendesk or Freshdesk briefs are also applied here, exactly one of them owns the user-facing form, the context capture, and the deduplication. This brief supplies only the Help Scout mapping and delivery on top of that shared path.
Edge cases it handles
8
Edge cases it handles
8- Matching a customer by email must not leak: the matched record's existing conversations must never be shown back to whoever submitted the form.
- A mailbox that was archived, deleted, or lost permission must fall back to a configured default and raise an operator alert rather than dropping the request on the floor.
- An assignee who has left the team must not silently swallow the conversation into a dormant inbox. Fall back to unassigned so the queue picks it up.
- Attachment metadata — original filename, type, and size — must survive the transfer, or agents receive a wall of unnamed binaries they cannot triage.
- A retry after a timeout must be matched on the request identifier, because the first attempt may have created the conversation before the response was lost.
- Rate limits and provider outages must queue the request with bounded backoff, and the user must be told their message was received rather than shown a provider failure.
- User-supplied text must be escaped before it is placed into rendered content, so a message containing markup cannot alter formatting or embed a link the sender did not write.
- The conversation identifier must be stored against the app record so a later reply threads onto the same conversation.
Definition of done
9
Definition of done
9- A request creates a conversation in the mailbox configured for that request type.
- The customer is resolved from the session and no matched history is exposed back into the app.
- Message formatting and attachment metadata arrive intact.
- A retried submission produces exactly one conversation.
- A missing, archived, or inaccessible mailbox falls back to a default and alerts an operator.
- Provider downtime queues the request and the user still receives a clear confirmation.
- The conversation reference is stored against the app record.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Mailgun Transactional Email
Mailgun Transactional Email
Send transactional email through Mailgun without losing bounce and complaint state.
What it does
A Mailgun delivery path bound to the correct region and sending domain, with durable suppression and event handling.
How it works
- 1 Put Mailgun behind the app's existing mail layer as one adapter. It is an alternative to the other transactional email integrations, not an addition; whichever adapter is in place, the template contract and suppression handling above it are unchanged.
- 2 Bind the region and sending domain in server-side configuration and validate at startup that they are consistent. A credential issued in one region will simply not work against another, and the failure looks like an authentication problem rather than a configuration one.
- 3 Check the suppression state for an address before a message is queued, not after the provider rejects it, so bouncing and complaining addresses stop consuming send attempts.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/mailgun-transactional-email
Firebase Cloud Messaging
Firebase Cloud Messaging
Deliver push through Firebase with registration tokens that stay valid as devices change.
What it does
A Firebase-backed push channel with server-side token lifecycle management, consistent payload handling across platforms, and safe handling of the routes a notification opens.
How it works
- 1 Store one record per device registration, tied to the account signed in at the time, the platform it came from, and when it was last confirmed working, and let one account hold many of them.
- 2 Send from the app's existing background-job system with the provider credentials held server-side, and treat every send as a job that can be retried rather than work done inline during a request.
- 3 Decide, per notification type, whether the payload is meant to be displayed by the platform or handled by the app, and keep that decision the same on every platform. The same event behaving as a visible alert on one platform and a silent update on another produces bugs nobody can reproduce.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/firebase-cloud-messaging
Slack Channel Alerts
Slack Channel Alerts
Send the events a team actually needs into a Slack channel without flooding it.
What it does
Operator-configured routing of selected app events into Slack channels, with grouping, throttling, and reliable delivery.
How it works
- 1 List the events genuinely worth interrupting a team for — failed payments, high-value signups, error thresholds, approvals waiting — and make each individually selectable per channel. An all-or-nothing firehose gets muted within a week and then nobody sees the one that mattered.
- 2 Run the connection through the provider's authorisation flow, then confirm the workspace and channel at setup by posting a test message the operator has to acknowledge. Store the resulting credential server-side only.
- 3 Write each message so it stands alone: what happened, to whom, when, and a link back into the app. Optional fields that are absent must be omitted cleanly rather than rendering as empty labels.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/slack-channel-alerts
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.