Draft a Support Reply With Full Context
For an agent who wants every reply to land right — aware of tier, history, and the last thing engineering told this customer. One prompt pulls the account context and drafts a tone-matched reply in seconds.
Every reply starts cold
Good support comes from knowing who you're talking to. Flipping between Zendesk and HubSpot to reconstruct context is what kills the response time.
Gold-tier customers treated like free-tier in generic templates
Missing the engineering update from last week's ticket
Tone falls flat — 'Thanks for your patience' in the fourth reply
Composio collapses all of this into one prompt — here's what that looks like.
Your agent runs it end-to-end.
- 01Fetch the current ticket's conversation
- 02Pull the account from HubSpot — tier, MRR, CSM, tags
- 03Pull the last 5 tickets for the same account
- 04Draft a reply that matches tier, references prior context
- 05Leave in Drafts for your review — never auto-send
Every reply lands in tone
Gold-tier customers get gold-tier replies. Repeat offenders get acknowledgment. Every draft references what engineering said — so you never contradict yourself.
Paste this into Claude, Cursor, or Codex. It'll install the CLI, connect your apps, and run the task — end to end.
Turn a Blog Post Into an Email Drip
Paste the blog. Your agent writes a 3-email nurture, picks the right HubSpot segment, and queues the campaign in Mailchimp — one prompt.
Read →Triage the Support Queue
Your agent groups unassigned tickets by urgency, tags by product area, and routes P0s to the on-call — every morning, on its own.
Read →Escalate a Support Ticket to Engineering
Your agent spots a real bug, files a Linear ticket with the repro, links it back in Zendesk, and pings the right engineering channel.
Read →