Subscriby Copilot
The operator inside Subscriby: ask it about your projects, members and money in plain words, have it do the routine work, and confirm anything that changes what already exists. Beside every dashboard page and inside your platform bot, on every plan, with free turns every month.
Subscriby Copilot is an operator that works inside your account. You tell it what you want in your own words, "who is about to churn?", "give Jane 20% off for three months", "create a project called Christmas Giveaways", and it answers from your live data or does the work, through the same operations the dashboard, the REST API and the MCP server use. It runs as you, with your permissions, and anything that changes or removes what already exists waits for your confirmation.
On every plan, with free turns every month
Every plan includes free turns each month (10 on Free, 25 on Starter, 50 on Growth), and beyond them a turn costs $0.10 from a prepaid pack. The Copilot never touches your plan invoice. Turns & Credits has the meter.
Three places to find it
Dashboard Panel
A sheet that slides in beside whatever page you are on and stays open while you move around. Press Ask Copilot in the sidebar or Ctrl+/.
Copilot in Your Bot
The platform bot your connector runs for you carries the same Copilot: Ask Copilot on its home menu and on every project card, then simply type.
Copilot in Your Inbox
A drafting hand in the Support Inbox: press ✨ beside your saved replies and a suggested reply appears above the composer, written from the thread. You read it, edit it and send it.
What it does for you
Answers you would click five pages for
Who paid this week, which trials end soon, why revenue dipped, what a Smart Link brought, how a plan performs against the others. It calls the right reads and answers with the figures.
Routine work in one sentence
A coupon for one member, a new plan, a reply in the support inbox, a Smart Link for a flyer: made at once, with a button to open it.
A card before anything that changes
A pause, a cancellation, a broadcast, anything that touches what exists, sends to members or moves money: prepared, shown with its exact arguments, run when you confirm.
Finding things
A member by name or by their connected account, a conversation, a payment, a plan, without remembering which page holds it.
A person for Subscriby questions
Your own invoice, a bug, how a feature works: it answers in a sentence if it can and hands you to the Subscriby team with a summary attached, so you never retype it.
Only what you can do
It holds exactly the permissions you hold. A team member's Copilot is bounded by their role, and every change is written to the activity log as the Copilot's, on your behalf.
The full list, area by area, is on Capabilities, and Example Conversations walks through real exchanges end to end. What only you know goes on the project's Knowledge page, questions with their answers and guides you upload: the inbox draft and the member answers read it today, the panel and the bot are next. Twice the Copilot speaks first, on Monday morning and when a project breaks its own pattern: Digest & Alerts has both.
A turn, step by step
You ask. Type in the composer, or tap one of the questions an empty thread offers. Write the way you would to a colleague who knows your business.
It works in the open. Between your message and the answer a timeline grows as it happens: the model's thinking as a faded line you can unfold, every tool as a step with the arguments it used hanging off it and the time it took, and "Working for 3s · 2 steps" counting above. Once the answer is in, it folds to one line, "Worked for 4.1s · 3 steps", and opens with a tap. In the bot the same work streams in the thinking preview.
The answer streams in, formatted as it arrives, with a View button for anything it made or read that has a page, and two or three follow-up questions you can send with one tap.
A card when it matters. If the work changes or removes what exists, sends to members or moves money, it stops first: a card names the action and its arguments and waits for Confirm or Cancel. Confirming runs it; cancelling costs nothing.
- Three signals matter here: failed payments in retry, cancellations at the end of the cycl…
Three signals matter here: failed payments in retry, cancellations at the end of the cycle, and trials ending without a card. The retention ledger and the member list cover all three.
- List retention activity0.4s
- project_id · Acme Club
- days · 14
- List subscribers0.3s
- project_id · Acme Club
- status · past_due
Three members are at risk. Jane Fox (Gold): her card failed twice, the next retry is on 20 October and she has four days of grace left. Tom Ray (Silver): cancelled at the end of the cycle, access ends 2 November; he answered "too expensive" on the cancellation screen. Priya N. (Gold trial): the trial ends tomorrow and no card is on file.
Nothing changed here: reads run at once and show no card. Tap Give Jane 20% off for 3 months and the next turn creates the coupon, which is new and runs at once too; ask it to pause Tom and you get a card first.
What it costs
| What you do | Turns |
|---|---|
| Send a message and get an answer | 1 |
| The same on the Lite tier | 1, however many steps |
| The same on the Max tier | 2, 4 past four tool steps |
| A message whose answer needed more than four tool steps | 2 |
| Confirm a card | 1 |
| Cancel a card, or a turn that failed | 0 |
Free turns come first, then the free part of your Copilot Credits, then the paid part, at $0.10 a turn. A suggested reply in the Support Inbox is not a turn: it costs $0.05 of Copilot Credits, never a free turn. Turns & Credits explains the order and the cap; Credits & Credit Packs covers the packs, the bonuses and how Copilot Credits differ from Subscriby Credit.
Copilot or MCP
Subscriby is agent-native: every operation the Copilot runs is also a tool on the MCP server, so Claude, ChatGPT, Cursor or an automation of your own can run your account too. Both roads lead to the same operations under the same permissions. They differ in who runs the model, where the conversation lives and what else is in the room.
| Subscriby Copilot | Your own agent over MCP | |
|---|---|---|
| Where it lives | Beside every dashboard page, in your platform bot and in the Support Inbox | Wherever you already work: Claude, ChatGPT, Cursor, n8n, code of your own |
| Setup | None. Press Ask Copilot | Connect once over OAuth from the assistant's connector settings |
| The model | Chosen and run by Subscriby, with a router that picks a lighter or a stronger model per message, or the tier you pick | Whichever your agent runs, with its own memory, files and other tools beside Subscriby |
| What it costs | Free turns every month, then Copilot Credits per turn | Nothing from Subscriby; your assistant's own plan or API bill |
| What it reaches | Your projects, members, money, support and Knowledge, as you | The same, bounded by the token's abilities and project scope |
| Before a change | A card with the exact arguments; Review every change asks for new things too | Your agent's own approval rules; every tool is marked read-only, additive or destructive, so a good client asks before the destructive ones |
| Your members | Answers their own-subscription questions and what your Knowledge covers, in the inbox, your bot and a chat on your portal page, on a separate agent with no tools | Never faces a member |
| The conversation | Kept in Subscriby for ninety days with every step, button and card | Kept by your agent |
| The record | Every change in the activity log as the Copilot's, on your behalf | Every change in the activity log as the token's |
Reach for the Copilot when
You are inside Subscriby and want the answer now, in the panel beside the page it is about; you want members answered while you sleep; you would rather not run an agent of your own.
Reach for your own agent when
Subscriby is one tool among several in a workflow, your team already lives in one assistant, or you want to script and schedule what the Copilot only does while you are talking to it.
The two are not exclusive. A team can press Ask Copilot in the dashboard in the morning and run the same operations from Claude in the afternoon, and the activity log tells the two apart.
Where it is going
The operator and the inbox are the first two of the Copilot's surfaces. Each of the next ones arrives with its own page here.
Answers for your members
Arrived: switched on per project, the Copilot answers a member's own-subscription questions and whatever your Knowledge covers, in the inbox, your bot and a chat on your portal page, marked as automated, on a separate agent with no tools. The Knowledge tools for the panel and the bot follow.
Monday mornings
Arrived: a digest in words every Monday at seven in your own time zone, with up to three steps worth doing, in the bell, by email and in your platform bot as your alert destinations say, and an alert when payments, cancellations or a payment rail on a project break pattern. Never charged.
Questions
Related
- Dashboard Panel — the sheet beside every page, end to end
- Copilot in Your Bot — the same operator inside your platform bot
- Capabilities — every area it reaches, what runs at once and what asks first
- Example Conversations — six exchanges as they happen
- Turns & Credits — what a turn is and how it is paid for
- Permissions & Safety — who may use it and what the model is shown
- Credits & Credit Packs — Subscriby Credit and Copilot Credits, side by side
How is this guide?
Last updated on
Troubleshooting
Fixes for the problems members hit most: failed payments, a bot that does not answer, missing group access and sign-in trouble.
Dashboard Panel
The Copilot sheet in the dashboard, end to end: opening it, the context chip, the start screen, threads, the composer, the work timeline and the streamed answer, View buttons and follow-ups, confirmation cards, the hand-off to live support and the credit line.