Subscription store pack

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.

Low score

This score or lower counts as unhappy: 6 on a 0–10 scale, 3 on 1–5.

Who calls back

The name the unhappy customer is told will call.

Feedback sheet ID

The Google Sheet the scores are logged to.

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 Intercom: Settings → Integrations → Developer Hub → New app (for their own workspace, no review) → Authentication → copy the access token. The conversation trigger needs the app to be allowed to read conversations.

• 

• Google Sheets

  In your own Google Cloud project: enable the Google Sheets API, then IAM & Admin → Service accounts → Create → Keys → Add key → JSON, and paste the file here. Then share each client sheet with the service account’s email (…@….iam.gserviceaccount.com) as an Editor. The account is yours; no Google review is needed.

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 Intercom, for “A new conversation comes in”
12. Connect the client’s Anthropic, for “Sort the message”
13. Fill in Topics (Comma-separated, the team’s own: billing, booking, complaint, technical, sales)
14. Pick the client’s form that starts it
15. Connect the client’s Twilio (SMS), for “Text the owner”
16. Connect the client’s Resend (email), for “Tell them a person will call” and “Thank them”
17. Connect the client’s Google Sheets, for “Log the score”
18. Fill in Low score (This score or lower counts as unhappy: 6 on a 0–10 scale, 3 on 1–5)
19. Fill in Who calls back (The name the unhappy customer is told will call)
20. Fill in Feedback sheet ID (The Google Sheet the scores are logged to)