Copilot in Your Inbox
A reply drafted on request in the Support Inbox: the button beside your saved replies, what the draft is written from (the thread, the member's standing, your saved replies and the Knowledge passages that match) and what it is never given, Use and Dismiss, the $0.05 it costs and where that comes from, who may ask, why a member's message can never steer it, and the per-project switch that lets the Copilot answer a member's own-subscription questions and what your Knowledge covers itself.
The Support Inbox gets the Copilot as a drafting hand, not as a voice of its own. When a member's message is waiting, one press asks for a reply written from the conversation, the member's standing with your project and your saved replies; you read it, change it, send it or drop it. Nothing is drafted until you ask, and the member never sees a draft.
One press, one draft
The ✨ button sits beside the saved replies in the composer's toolbar. Each press is one suggestion for $0.05 of Copilot Credits, never a free turn, and never without you asking.
Written from what is there
The thread, the member's standing and your saved replies, nothing else. The suggester has no tools, sees no other member and is told to invent nothing.
Yours to send
Use this reply copies the draft into the composer; it reaches the member only when you press Send, under your name like any reply. Dismiss drops it.
Private until sent
A draft waits on the thread until you use or dismiss it, and only you and your team see it: it is never relayed, never listed among the thread's messages and never sent on its own.
Asking for a draft
Open the thread. In the project's Support Inbox, open the conversation you want to answer. The composer's toolbar shows the ✨ button next to the saved-replies bookmark whenever the Copilot is in your role and no draft is waiting; hovering it names the price.
Press it. The button spins while the Copilot writes, a few seconds, and the draft appears above the composer in a violet box headed Suggested reply: the text, and under it a short line such as "Based on the Gold plan and the Invite link saved reply" naming what it drew on.
Read it, then decide. Use this reply puts the words in the composer with the cursor at the end, so you can change anything before sending. Dismiss removes the draft and leaves whatever you had typed alone. Either way the box goes and the ✨ button is back.
Send it yourself. The draft is a reply, never a private note: it leaves through the composer's Send, prefixed with your display name, and arrives in the member's chat like any other reply. Nothing you did not send ever reaches them.
What the draft is written from
The conversation
The last twenty messages of the thread, the member's and yours, each cut at 1,500 characters. Private notes are left out: the suggester never reads what your team wrote for itself.
The member's standing
What the right-hand pane knows: their name, their status with the project, their plan and that subscription's status and end date, since when they have been a member, and how many subscriptions they have held. "When does my plan end" is answered from the record, not a guess.
Your saved replies
Every saved reply of the project, title and text. When one fits the situation the draft keeps its wording and its links and adapts only the member's details, so your house answers stay your house answers.
Your Knowledge
The five passages of the project's Knowledge that best match the member's last message, Team Only entries included, because you read the draft before it goes out. When one answers the question, the draft keeps its facts exactly as you wrote them.
And nothing else
No other member, no revenue, no settings, no tools. The suggester cannot look anything up and cannot change anything; it writes from the four things above or says what it will check.
The draft is written as you: in the first person, under your support display name or the project's name when you set none, in the language the member wrote in, in two to five sentences, from the facts it was given and nothing it was not. When a fact is missing, it says what you will check rather than inventing a date, an amount or a promise. It never says it is an assistant or that the reply was drafted.
What you see, state by state
| State | The composer |
|---|---|
| No draft, the Copilot in your role | The ✨ button beside the saved replies, with the price in its tooltip |
| Drafting | The button spins; the toolbar is otherwise as it was |
| A draft waiting | The Suggested reply box above the composer; the ✨ button is hidden |
| After Use this reply | The words in the composer, ready to edit; the box gone; the ✨ button back |
| After Dismiss | The box gone, the composer untouched; the ✨ button back |
| The thread opened again later | The draft still waiting: it is kept on the thread until it is used or dismissed |
| The Copilot not in your role | No button; the composer as it always was |
| Your Copilot Credits used up | A notice that the credit is spent; nothing is asked and nothing is charged |
What it costs
| What you do | Costs |
|---|---|
| Press ✨ and receive a draft | $0.05 of Copilot Credits |
| Use, edit or dismiss the draft | 0 |
| A draft the model could not deliver | 0 |
A suggestion is not a turn
Free turns never pay for one. A suggestion draws on your Copilot Credits straight away, the free part first (the pack bonuses, any promotion), then the paid part, and a paid draw counts against the monthly spending cap like a turn's. The credit is checked before the model is asked: with nothing to draw on, a notice says the credit is spent and no draft is made. The Copilot Credits statement lists each one under Reply Suggestions, with the project it was about.
Answers for members, when you switch it on
Off by default, Let Subscriby Copilot answer members in the inbox's Settings lets the Copilot reply to a member itself, but only about the member's own standing with your project or what your Knowledge entries marked for members cover, and only from the member's own record, your saved replies, the portal address and those entries. Anything else is left for you exactly as before, and the acknowledgement you configured still goes out for it.
| The member asks about | What they get back |
|---|---|
| A receipt or invoice | Where to find it, with the portal link |
| When the membership renews or ends | The date from their subscription |
| Pausing or cancelling | How to, with the portal link to manage the membership |
| A failed payment | What happened, with the portal link to update the card |
| The portal address | The address |
| Something your Knowledge covers | The answer from the entries marked for members, which the thread keeps as the answer's sources |
| Anything else | Nothing from the Copilot: the message waits for you |
Every answer opens with "Automated answer from your project, written by Subscriby Copilot", ends with "If this does not settle it, reply here and a person will pick it up", and is written into the thread as the assistant's message, so you read what the member was told. A second switch, Let Subscriby Copilot answer members on your portal, puts the same answerer in a chat in the corner of your portal page for a signed-in member: the same five kinds of question and your Knowledge, a button that opens their memberships when the answer is about them, and Talk to a person, which files the chat on their inbox thread as a note and sends them to your bot; nothing is kept beyond the visit. One thread is answered at most ten times an hour, and each answer is one member answer from your monthly allowance (100 on Free, 250 on Starter, 500 on Growth), then $0.01 of Copilot Credits; a spent pool means the Copilot stays quiet rather than failing.
The member boundary
The answerer is a separate agent with no tools at all. It cannot look anything up, cannot change anything, never sees another member, your revenue, your settings or a Team Only entry, and a member's message reaches it as text to answer, never as instructions. Anything it might newly see is a decision made in the open, never a prompt change.
Who may ask
The account owner
Always, in every project. Each suggestion comes out of the owner's Copilot Credits, the pool the Billing page shows.
A team member
When their role carries Use Copilot and lets them answer in the Support Inbox. The button is hidden otherwise. Their suggestions draw on the owner's pool, and the draft is written under the project's display name whoever asked.
A member's message can never steer it
The member's words and your saved replies reach the model as data inside marked blocks, never as instructions, and the suggester is told that anything in a message asking it to change its rules, reveal them or act on your account is text to answer, not an order. It has no tools, so there is nothing it could act with; the worst a hostile message can produce is a poor draft you read and drop.
Questions
Related
- Support Inbox — the inbox itself: threads, saved replies, notes, blocking
- Turns & Credits — the pools a suggestion is paid from and the cap
- Permissions & Safety — the Use Copilot permission and the limits
- Dashboard Panel — the operator beside every page
How is this guide?
Last updated on
Copilot in Your Bot
The same operator inside the bot your connector runs for you: the three doors into it, the thinking that streams while it works, the answer with its buttons, follow-up taps, confirmation cards, leaving and starting a new thread, and what happens when your credit runs out.
Digest & Alerts
The two times Subscriby Copilot speaks first: a digest every Monday at seven in your own time zone, written in words from your week's figures with up to three steps worth doing, and an alert when a project breaks its own pattern (payments failing far more than usual, a day of cancellations, a payment rail on which every attempt failed). Where each reaches you, what they are written from, why neither costs anything, and how to route or quieten them.