Skip to content

Pack · Software development agency

Retainer dev agency pack

A retainer dev agency keeps clients on monthly support with response times per severity, so triage speed is the product.

Start the 14-day trial, then find it under Templates → Library. It installs into the client you choose, switched off, with its checklist.

Workflows
3
Steps
12
Client fills in
9
Starts
From Zendesk, Slack or Stripe, within 5 minutes

UsesBeta

The workflows in this pack

Built for software development agencies.

  1. 01

    Ticket triage for software development agencies

    Acknowledge every support ticket at once, sort it by topic and urgency, page someone for the urgent ones, and tell the team.

    1. Starts whenA ticket is opened
    2. AgentSort the ticket
    3. Zendesk: Update a ticketAcknowledge it
    4. BranchUrgent?
    5. IfIf yes
    6. TextText whoever is on call
    7. IfIf no
    8. App stepPost to the team
  2. 02

    Request to task for software development agencies

    Turn every request posted in the requests channel into a task in the team’s list, and reply in the channel with the link.

    1. Starts whenA message is posted in a channel
    2. AgentWrite the task
    3. App stepNamed by the agent
    4. App stepSay where it went
  3. 03

    Failed payment recovery for software development agencies

    When a card payment fails, send the customer a plain, kind message with the link to pay, by email and text, and tell the owner.

    1. Starts whenA payment fails
    2. EmailTell the customer, kindly
    3. BranchDo we have a mobile?
    4. IfIf yes
    5. TextAnd by text
    6. IfIf no
    7. NotifyTell the owner

What each client fills in

Business name
How messages sign off.
AI model
The model the client’s key can use.
Topics
Comma-separated: billing, bug, how-to, account.
When a person replies
One sentence the customer reads: “We answer within one working day.”
Owner’s mobile
Texted when something needs a person now.
Team channel
The Slack channel that hears about it.
Requests channel
The Slack channel where people ask for things.
Task list ID
The ClickUp list the tasks go into.
Owner’s email
Gets the summaries and the cases a person must handle.

The accounts it needs

Each is the client’s own, stored encrypted and never copied between clients. Until one is added the client’s checklist shows it, and nothing runs.

  • In the client’s Zendesk: Admin Center → Apps and integrations → APIs → Zendesk API → enable Token access → Add API token. The triggers make webhooks, which needs an admin’s email and token.

  • platform.claude.com → Settings → API keys → Create key, in the workspace that bills this client.

  • In the client’s Slack: api.slack.com/apps → Create New App → OAuth & Permissions → add the chat:write scope (and channels:history, plus groups:history for a private channel, for the message trigger) → Install to Workspace → copy the Bot User OAuth Token. Invite the app to the channel.

  • In the client’s ClickUp: avatar → Settings → Apps → API Token → Generate.

  • In the client’s Stripe dashboard: Developers → API keys → Create restricted key. Give it only what the steps need: Customers write, Payment Links write, Prices read, Invoices write, and Webhook Endpoints write for the triggers. Leave “IP access” empty: Thrum has no fixed addresses, so a key locked to IPs fails every call.

After you install it

It lands switched off. The client’s checklist holds exactly this:

  1. Connect the client’s Zendesk, for “A ticket is opened” and “Acknowledge it”
  2. Connect the client’s Anthropic, for “Sort the ticket”
  3. Connect the client’s Twilio (SMS), for “Text whoever is on call”
  4. Connect the client’s Slack, for “Post to the team”
  5. Fill in AI model (The model the client’s key can use)
  6. Fill in Business name (How messages sign off)
  7. Fill in Topics (Comma-separated: billing, bug, how-to, account)
  8. Fill in When a person replies (One sentence the customer reads: “We answer within one working day.”)
  9. Fill in Owner’s mobile (Texted when something needs a person now)
  10. Fill in Team channel (The Slack channel that hears about it)
  11. Connect the client’s Slack, for “A message is posted in a channel” and “Say where it went”
  12. Connect the client’s Anthropic, for “Write the task”
  13. Connect the client’s ClickUp
  14. Fill in Requests channel (The Slack channel where people ask for things)
  15. Fill in Task list ID (The ClickUp list the tasks go into)
  16. Connect the client’s Stripe, for “A payment fails”
  17. Connect the client’s Resend (email), for “Tell the customer, kindly” and “Tell the owner”
  18. Connect the client’s Twilio (SMS), for “And by text”
  19. Fill in Owner’s email (Gets the summaries and the cases a person must handle)

Thrum is cooking.

Get early access and you’ll be among the first in. Early members get a launch perk.