> ## Documentation Index
> Fetch the complete documentation index at: https://build.practicehub.io/llms.txt
> Use this file to discover all available pages before exploring further.

# What can it actually do?

> A plain-language tour of what a connected assistant can do in your clinic

Once you've [connected an assistant](/mcp/connectors), you can talk to it like a capable new team member who's read the manual — it can look things up, check the diary, and answer questions about your own PracticeHub account. This page is a tour of that, in plain language, with no code.

<Note>
  **During the limited rollout the assistant is read-only.** It can look anything up, but it cannot book, cancel, take payments or change records yet — you make those changes in PracticeHub as usual. The write abilities described in places below are what's coming when the rollout widens; today the server simply doesn't offer them, so the assistant physically has nothing to call.
</Note>

## What it can do, in human terms

* **Look things up** — a patient's details, their appointment history, what they owe, which invoices are unpaid, which appointment types are bookable online, and so on.
* **Check availability** — find genuinely free slots for a location, appointment type and (optionally) a specific practitioner, ready for you to book in PracticeHub.
* **Coming later — book, change and record** — booking and rescheduling, recording payments, updating records and conversational data migration arrive when write access is switched on.

It only ever does what the person who connected it is allowed to do in PracticeHub — see [Boundaries](#boundaries) below, and [Administration](/mcp/administration) if you're the one deciding who gets to connect one.

## Example asks

<AccordionGroup>
  <Accordion title="“What does my Thursday look like?”" defaultOpen>
    It looks at your own diary for Thursday and reads back what's booked — patients, times and appointment types. Ask it to also flag anyone who hasn't confirmed, and it can filter by status too.
  </Accordion>

  <Accordion title="Coming later — “Book Mrs Ellis's follow-up next Tuesday afternoon with Dr Patel.”">
    <Warning>Not available yet: the assistant is read-only during the limited rollout. This is how it will work once changes are switched on.</Warning>

    It finds Mrs Ellis, works out which appointment type "follow-up" means for her, checks Dr Patel's genuinely free slots on Tuesday afternoon, and — a well-behaved assistant will do this — reads the details back to you before booking. Once you say yes, it's a real booking: validated the same way the calendar is, with the usual confirmation message sent, and it shows up in the appointment log as booked by you.
  </Accordion>

  <Accordion title="“Which invoices are unpaid this month?”">
    It pulls up every unpaid invoice dated this month. This needs your role to have financial visibility switched on — if it can't see invoices, it'll tell you that rather than guess.
  </Accordion>

  <Accordion title="Coming later — “Move my 10 o'clock to 2pm.”">
    <Warning>Not available yet: the assistant is read-only during the limited rollout. This is how it will work once changes are switched on.</Warning>

    It checks 2pm is actually free first (so it isn't double-booking you), then moves the appointment, keeping its original length unless you say otherwise. If the slot's taken, it says so instead of forcing it in.
  </Accordion>

  <Accordion title="Coming later — “Cancel Mr Byron's 3pm today, he's called in sick.”">
    <Warning>Not available yet: the assistant is read-only during the limited rollout. This is how it will work once changes are switched on.</Warning>

    It cancels the visit with a note recording why, and the normal cancellation messaging goes out to the patient — exactly as if a staff member had clicked cancel. If the visit's already been checked out, it can't be cancelled, and the assistant will tell you that instead of trying to work around it.
  </Accordion>

  <Accordion title="Coming later — “Add a note to Ada's file — she brought in a referral letter.”">
    <Warning>Not available yet: the assistant is read-only during the limited rollout. This is how it will work once changes are switched on.</Warning>

    It adds a dated entry to Ada's patient record. This needs your role to be able to edit patients; without that, it'll say so rather than silently skip it.
  </Accordion>

  <Accordion title="Coming later — “Take £45 cash from Bob and allocate it to his open invoice.”">
    <Warning>Not available yet: the assistant is read-only during the limited rollout. This is how it will work once changes are switched on.</Warning>

    It records the payment and applies it to the invoice, the same way you would at the desk. Card payments are the one payment type it can't record this way — it'll point you at the card terminal instead.
  </Accordion>

  <Accordion title="Coming later — “Here's our patient list from the old system — bring it into PracticeHub.”">
    <Warning>Not available yet: the assistant is read-only during the limited rollout. This is how it will work once changes are switched on.</Warning>

    Not yet — this is a write, and the assistant is read-only during the limited rollout, so it cannot create records. Migrate over the REST API instead ([Importing your data](/guides/importing-your-data)); assistant-driven migration arrives when write access is switched on — see [Migrating your data](/mcp/migrating-your-data) for why and when.
  </Accordion>
</AccordionGroup>

## Boundaries

* **Clinical notes follow your note permission.** The assistant can read a patient's notes when your role has *Patient visit notes* — the same permission that shows the notes tab in PracticeHub itself — and the own-patients ringfence narrows it the same way it narrows everything else. It cannot write notes during the limited rollout. Once write access is switched on, the same permission will let it create a note, filed against one of the account's own note templates (a role limited to draft-only notes will only create drafts); editing or deleting a note, adding a signature or drawing, or submitting AI Scribe audio stay app-only.
* **Documents and scans need the other route.** Uploading a PDF or image isn't something you can hand an assistant conversationally today; that goes through the [REST API's document upload](/guides/data-migration#6-documents) instead, typically with a developer's help.
* **Card payments can't be recorded through it.** Cash, bank transfer and the like, yes — card payments have to go through your card terminal as normal.
* **It can only do what your role allows.** Not a technical limit you need to think about day to day — but if it refuses something, that's your PracticeHub permissions working correctly, not a fault. See [Troubleshooting](/mcp/troubleshooting) if a refusal looks wrong, and [Administration](/mcp/administration) to change what a role can do.

<Tip>
  A good habit with any assistant: ask it to read back what it's about to do before a booking, cancellation or payment, and to tell you plainly when something's refused rather than trying to route around it.
</Tip>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.