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.
The Copilot panel is a sheet that slides in from the right of any dashboard page. The page keeps its width and stays readable behind it, and because the panel is mounted once in the layout it keeps your thread open while you move between pages.
Your first turn
Open it. Press Ask Copilot in the sidebar, under the search, or press Ctrl+/ (⌘+/ on a Mac). The shortcut is printed beside the sidebar entry, the way the search shows its own.
Check the chip. Under the header a chip names what the Copilot is looking at: the project whose page you are on, or Overall Dashboard when you are on none. That context travels with every message.
Ask. Type in the composer and press Enter, or tap one of the nine prompts the start screen offers. Shift+Enter breaks a line. The small Auto button beside Send picks the model tier and switches review on.
Watch it work. A timeline grows between your message and the answer: the thinking as a faded line, every tool as a step with its arguments and the time it took, "Working for 3s · 2 steps" counting above; then the answer arrives word by word, formatted.
Act on the answer. Press a View button to open what it made or read, tap a follow-up to send the next question, or Confirm a card when it asks before changing something.
The panel, piece by piece
Header
The Copilot's mark and name, a Threads button that lists your recent conversations with New thread at the top, and the close button. Esc closes it too.
Context chip and the eye
The project or page in view, and, while the eye beside the chip is lit, the text of the page itself, read at the moment you send: what is on screen first, the rest of the page after it, up to 8,000 characters. So "why is this one red?" or "add up this column" works on any page, and "pause the subscription of the member I have open" needs no name. Tap the eye to keep the Copilot off a sensitive page; your browser remembers the choice. What it reads counts toward the turn's tokens, never as an extra turn.
Start screen
An empty thread shows eight day-to-day questions, each a quick read that changes nothing: who is about to churn, who joined this week, who is past due, this month's earnings by plan, and more. Tap one and it is sent as if you had typed it.
Transcript
Your messages on the right, the Copilot's under its mark, each answer's work folded to one line above it ("Worked for 4.1s · 3 steps"), the View buttons, the follow-ups and the cards. Under every answer a small line says what it used: the tier and the model that answered, the prompt tokens with the cached part, the output tokens, the time, and whether it was a free turn or one from your Copilot Credits. Speak Aloud at the head of that line reads the answer: the first time it says Generating with an estimate counting down, learned from how fast the voice has been for you, then Stop while it plays; a natural voice for English, your browser's own voice for the other languages. Once you have used it, each new answer's voice is prepared in the background as the answer arrives, so the next press plays at once. A table in an answer is shown as a card per row.
Composer
One line that grows as you type, up to six, with the model button, the microphone and the send button beside it. A message may be up to 4,000 characters, in any language. Tap the microphone and the field becomes a recorder: a clock, a live spectrum of your voice, and the microphone and send buttons become discard and done where they stand. Done turns the recording into words in the composer, after whatever you had typed, and leaves sending to you, so a misheard request never runs. A recording may be up to a minute; the words are free.
Credit line
Under the composer: "24 free turns left this month · $5.00 Copilot Credits". When both are spent it reads "No turns left this month and no Copilot Credits" with a Top up link.
Keyboard
| Keys | Does |
|---|---|
| Ctrl+/ | Opens the panel, and closes it again |
| Esc | Closes the panel |
| Enter | Sends the message |
| Shift+Enter | Breaks a line inside the message |
Who sees the entry
Ask Copilot is shown only to people who may use the Copilot: the team owner, a creator with no team, and any team member whose role carries Use Copilot. A member whose role lacks it sees "Copilot is not in your role" instead of the composer, and nothing is charged (Permissions & Safety).
Threads
The Threads button in the header lists your recent threads, newest first, each named after its first message, with New thread at the top. Open an old one and the whole conversation is there, with each answer's work timeline, its buttons and its cards. A thread nobody has used for ninety days is removed.
A thread opened from a project page stays about that project for its whole life; a thread opened elsewhere takes the project in view turn by turn. When no project is in view and the request needs one, the Copilot lists your projects and asks which, unless you have only one.
While a thread is open, the ⋯ menu beside Threads offers two more things:
| Action | What happens |
|---|---|
| Archive thread | The thread leaves the list and nothing continues it, in the dashboard or in your bot, which starts a fresh one. It keeps its conversation and sits under Archived threads in the switcher, where one tap restores and opens it. |
| Delete thread permanently | After you confirm, the thread goes for good with its conversation, its tool runs and its cards. There is no undo. |
A message whose turn could not run, because the model was unreachable or the credit was spent, leaves no thread behind: the notice appears, your words go back into the composer, and the switcher stays as it was.
Model and review
The Auto button beside Send opens the model menu. Auto, the default, lets the Copilot pick the model for each request; the three named tiers pin one, and the dots beside each say what a turn on it costs.
| Tier | Best for | What a turn costs |
|---|---|---|
| Auto | Everyday use; the router picks per request | 1 turn, 2 past four tool steps |
| Lite | Quick reads and simple edits | 1 turn, however many steps |
| Pro | Sharper answers and multi-step work | 1 turn, 2 past four tool steps |
| Max | Deepest reasoning for the hardest requests | 2 turns, 4 past four tool steps |
Under the tiers, Review every change makes every tool that writes wait for a card, the additive ones included, so a new coupon or a new project is shown to you before it exists. With review off, only changes to what already exists wait (Capabilities). A thread remembers the tier and the switch you last used on it; the bot always runs on Auto.
While it works
The work timeline
Between your message and the answer a timeline grows as the turn runs: the model's thinking as a faded line with a hollow dot, every tool as a step with the arguments it used hanging off it on a braid of lines and the time it took at the right, and "Working for 3s · 2 steps" counting above. A running step shows a hollow dot too.
Folded once it is done
When the answer is in, the work folds to one line, "Worked for 4.1s · 3 steps". Tap it to open the rail again, tap a thought to read it in full; a failed tool shows a red dot with "Failed" under it, a cancelled card a grey one.
The answer
Streamed word by word and rendered as it arrives: bold, lists and short tables read correctly even mid-sentence.
After the answer
View buttons
When a turn made or read something that has a page, a purple button opens it: View Christmas Giveaways for the project it just created, Open the plans for a list it worked through, View Jane Fox for a member. The button navigates without leaving the thread.
Follow-ups
Under the latest answer, two or three secondary buttons with the requests you are likely to make next, phrased as you would type them ("Add a plan to it", "Connect a bot"). Tap one to send it.
The page refreshes
A turn that changed something refreshes the page behind the panel, so a coupon it created appears in the table beside you.
Confirmation cards
Anything that changes or removes what already exists, sends to members or moves money stops before it runs; creating something new does not (Capabilities). An amber card shows Confirm before I do this, the operation in words, every argument it will use, and two buttons.
- List subscribers0.3s
- project_id · Acme Club
- search · Tom Ray
- Pause subscription
- subscription_id · Tom Ray, Silver
- resume_at · 1 November 2026
- subscription_id
- Tom Ray, Silver
- resume_at
- 1 November 2026
Confirm runs it and the Copilot finishes its answer; Cancel declines it, and nothing happens. A card expires after ten minutes; ask again and the Copilot prepares the action afresh. Confirming counts as a turn, because the Copilot reads the result and writes its answer; cancelling is free.
One card, one action
The Copilot never splits a destructive action into smaller pieces to avoid the card, and never repeats an action you cancelled. A tool that refuses because your role does not allow it is reported plainly; it does not look for another way round.
Questions about Subscriby itself
The Copilot is not Subscriby's support desk. Ask about your own Subscriby invoice, a bug, an outage, how a feature works or something you wish existed, and it answers in a sentence if it can, then hands you over: the live-support chat opens in the corner with the topic and a summary of what you asked already attached, so a person from the Subscriby team continues with you without you retyping anything.
The credit line, state by state
| The line reads | Meaning |
|---|---|
| 24 free turns left this month · $5.00 Copilot Credits | Turns draw the free allowance first; the credit is untouched until it is gone |
| 0 free turns left this month · $5.00 Copilot Credits | Every turn now draws $0.10 from the credit, free part first |
| No turns left this month and no Copilot Credits · Top up | The composer refuses to send until you top up or the month turns |
Turns & Credits has the whole meter.
When something goes wrong
| You see | What it means |
|---|---|
| "The Copilot could not reach its model" | The provider did not answer; nothing was charged. Try again in a moment. |
| "This answer failed before it finished. Nothing was charged for it." | The turn broke mid-way; the thread keeps the note and you pay nothing |
| A red dot on a step of the work, "Failed" under it | That tool failed; the Copilot says what it could not do |
| "Copilot is not in your role" | Your role lacks Use Copilot; ask the team owner to add it |
Questions
Related
- Copilot in Your Bot — the same conversation inside your platform bot
- Capabilities — the operations, and which ones ask first
- Example Conversations — six exchanges end to end
- Turns & Credits — the meter behind the credit line
How is this guide?
Last updated on
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.
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.