What can an AI assistant do in my Scribble account?
Eighteen tools, covering everything you would do in the app except designing a card and managing your team: send one card or a merged batch, set up a recurring birthday rule, load contacts in bulk, and look anything up. Only three of them can spend a credit, and each is flagged so your assistant asks you first.
On this page
#The four permissions
You choose these when you connect, and you can reconnect at any time to change them. An assistant is only offered the tools its permissions cover — the rest are not in its list at all, so it cannot try and fail.
| Permission | What it unlocks | Can it cost money? |
|---|---|---|
| See cards you have sent | Card lists and status lookups | No |
| Send handwritten cards | Sending, and cancelling | Yes — one credit per card |
| Read your address book | Looking someone up by name | No |
| Add and update contacts | Saving a new contact | No |
#The four things people actually ask for
| What you say | What happens |
|---|---|
| Send a thank-you card to Dana for the introduction | Looks her up, drafts it, checks the address, and asks you before posting. |
| Here is my customer spreadsheet — add them to Scribble | Saves up to 500 at a time and tells you how many have a postable address and how many have a birthday on file. |
| Send a thank-you to all forty of them, personalised | Builds the batch, fills in each person's name, checks every address, and shows you two real merged cards before anything is sent. |
| Set up birthday cards for that list | Creates the rule switched off, tells you how many people it can act on, and waits for you to turn it on. |
#Tools that only read
- get_scribble_account
- Which organization the connection belongs to, the credit balance, and what was granted. This is the connection test.
- get_credit_balance
- How many cards can still be sent, excluding credits already promised to scheduled campaigns.
- list_handwriting_styles
- The handwriting styles on offer, grouped into Everyday, Quick, Flowing, Print, Classic and Wildcard, with what each group means.
- list_card_designs
- Your saved card designs, so the assistant can pick one by name instead of asking for an id.
- find_contacts
- Searches your address book by name, email or company, and says who is missing a mailing address.
- list_sent_cards
- Cards you have sent, newest first, filterable by status.
- get_card_status
- One card in detail: every production step, the arrival window, and whether a carrier scanned it.
- check_card_before_sending
- A dry run. Validates the address, the message length, the handwriting and the balance, and reports every problem — without sending and without spending anything.
- list_contact_lists
- The lists in your account, with how many people are on each. A list is what a batch or a rule is aimed at.
- list_recurring_card_rules
- Your rules, whether each is on, and — the number that matters — how many contacts each can actually act on.
- search_scribble_docs
- Searches these pages, so the assistant answers questions about pricing and turnaround from what is actually written here rather than from a guess.
#Tools that change something
- save_contacts
- Adds up to 500 people to the address book at once, or updates them if they are already there. Reports how many can actually be posted to, how many are missing a birthday, and who is on the do-not-mail list. Cannot delete anybody.
- prepare_card_batch
- Builds a run of up to 1,000 cards from a list and one message with merge fields. Sends nothing and uses no credits — it fills in every card, checks every address, and hands back two real examples plus everything that is blocked.
- create_recurring_card_rule
- Creates a birthday, work-anniversary or custom-date rule. Always saved switched OFF, with a count of how many contacts it can act on.
- send_card — flagged irreversible
- Writes and posts one real card. Spends one credit. Marked as a destructive action so that every compliant assistant asks you to confirm the exact call first.
- send_card_batch — flagged irreversible
- Posts every ready card in a prepared batch, using one credit each. If the run is over your organization's approval threshold it is parked for an owner to sign off instead of going out.
- activate_recurring_card_rule — flagged irreversible
- Switches a rule on, so it starts sending by itself. Refused if the rule can match nobody. Switching a rule off is always allowed.
- cancel_card — flagged irreversible
- Stops a card and returns the credit, but only while it is still waiting for a machine. Once a pen is on the paper the answer is a plain no with the reason.
#Two deliberate pieces of friction
#The do-not-mail list is honoured everywhere
Anyone on your do-not-mail list is refused before a card is made — by a single send, inside a batch, and by a recurring rule. Nothing is charged. This is matched on their postal address, and on their email too when the assistant has one, because that is how most opt-out requests arrive.
#What an assistant still cannot do
- Design a card. That is a visual job and belongs on a canvas.
- Approve a big run. If your organization requires sign-off above a card count, an assistant's batch waits for a person exactly like anyone else's.
- Register a webhook, mint an API key, or change your default handwriting or return address.
- Delete a contact, a list or a rule.
- Manage your team.
#Duplicate protection
If the same card — same words, same person, same address — is sent twice within 24 hours, the second one is refused and the first is returned instead. A dropped connection makes an assistant retry, and a retry must not put a second card through somebody's door. If you genuinely want to send the same card twice, give the second one a different reference.
Last checked against the product on . Something wrong or missing? Tell us.