Meet George, Your AI Assistant (1:18 video). Open on its own page
Auto mode: changes you can undo just happen
George is a help agent first: he looks things up, explains, and links you to the right page. He can also make almost any change you could make in the dashboard. By default he works in Auto mode: a change you can undo (adding a customer or a note, renaming the business, creating a service, rescheduling a visit) just happens when his reply ends, and its card shows Done with an Undo button. Anything that sends a text or email, moves money, deletes something, or changes billing still appears as an approval card, and nothing happens until you click Approve or reply "yes" / "go ahead". A change he stages from a script (many records at once) always asks too. So do a few kinds of change that are easy to undo but shape what George and the phone assistant do next: saving or changing a remembered fact, adding a phone-assistant instruction, creating or editing an automation, adding or editing an employee, and changing who receives your emails, texts or calls (sender address, texting settings, review link, blocked numbers, call routing). And when George is working from a text message or inside an automation, with nobody watching the chat, every change waits on a card.
The Auto / Ask switch under the message box in the George chat controls this for your messages on that device: click it to Ask and every change waits for your approval; click again for Auto. It starts on Auto.
Every company has George's change abilities — there is nothing to switch on, no rollout to wait for, and no setting Pool Founder has to flip for you. The safety net is Undo plus the approval card: actions start at Auto (the ones Undo can reverse run, the rest ask). On the George Permissions page, Ask makes an area or action always wait for your approval, Always skips the card for that one action even when it cannot be undone (for you only), Never hides the action from George, and a few actions (archiving, completing work orders, importing a spreadsheet) always ask no matter what. What George offers you also follows your own role: he can only prepare a change your role could make in the app yourself, so someone without the Create customers permission is never offered "create a customer". If George gives you steps and a link instead of a card, it is one of three things: an action he has no tool for (see the list below), an action set to Never (by you, or company-wide by an owner), or a permission your role does not have.
Approval cards work the same in the technician mobile app (the Ask George button, for owners and admins). Ask George on your phone to make a change and the same "George wants to:" card appears in the conversation, under his reply: the steps, Approve and Decline buttons, and Always allow… when the action can skip the card. Replying "yes" approves it too. After you approve, the card turns into a receipt (Working… while background steps run, then Done, Partially done, or Failed with a ✓ or ✗ per step) with an Undo button for 15 minutes when the change can be undone. Approving, declining, and undoing need a connection; offline the buttons dim and the card reads "You're offline. Approve or decline once you're back online."
What George can change today
George can prepare almost any change you can make yourself in the dashboard, always behind an approval card (each kind of change is listed on the George Permissions page, grouped by the part of the app it changes). Ask in plain words; he finds the right action, looks up the records, and prepares the card:
- Adding and editing customers: add a customer, edit, tag, merge, archive or unarchive customers; add a service location to a customer or correct where it is and its gate notes; change a customer's billing address; add notes to a customer, job or location; turn a customer's automated texts on or off (this only allows a text: it still needs that text's company-wide switch on under Messages → Phone → Automated texts, SMS consent, and a phone number on file, and George tells you if one is missing); bodies of water, equipment and water chemistry readings; leads and referrals. George chains a new customer, location, job and route onto one card: "add Jerry Alvarez at 12 Main St, weekly Tuesdays with Mike".
- Jobs, work orders and visits: add and edit recurring services and work orders (rate, name, checklist, preferred days and technicians, seasonal schedule, how it is invoiced), suspend, resume or archive a job, log a visit from the office, and correct a past visit's rate, chemicals, parts, costs or checklist.
- Routes and scheduling: put a job on a route, move a customer to another route or day for good, change how often they are serviced, move or skip a single visit, hand a day's route to another technician, move the rest of a technician's stops, create one-off stops, add a task for just the next visit, take a job off a route without archiving it, report an issue, and mark a stop completed. Ask him to "start my route" and he starts your own route for today; he can also start another technician's route for them from the office (it goes live on their phone and they get a notification). If you ask him to mark a stop done on another technician's route today, the visit is credited to that technician and their stop is marked done, and George tells you who it was credited to.
- Invoices and quotes: create an invoice, send or resend it, record a check or cash payment, add a charge or discount to the next invoice, turn AutoPay on or off, request a card on file, create, edit and send quotes, and mark a quote accepted or declined.
- Texts and the inbox: text one customer from your business line ("tell Mrs. Smith we're running late"), reply to a service request or a Google review, approve or dismiss the texting assistant's drafts, and change automated-text settings.
- Team, inventory and settings: add and edit employees and their schedules, set how a technician is paid (their pay model), send invites, vehicles and mileage, chemicals, parts and inventory purchases, task templates and services (on George Permissions these read, for example, Create a recurring service, Edit recurring services, Archive recurring services, Restore archived recurring services, Copy recurring services, Switch a pool to another recurring service, Create work order services, Edit work order services, Archive work order services, Restore work order services, Duplicate work order services, Add starter services and Create several recurring services), and most company settings pages.
- Importing a spreadsheet of customers attached in the chat, and recurring services (both below). An import happens only when you click Import on its sheet or approve George's card, and has no Undo.
- Remembering facts: "remember that…" / "forget that…" (see What George remembers below).
Anything that emails or texts a customer, records or changes money, archives, deletes or merges, or changes many records at once always shows a card, even if you set that action to Always. A card that emails someone or talks to Stripe or QuickBooks shows Working… for a moment after you approve and updates when it finishes.
You can approve in the chat. Once a "George wants to:" card is waiting, replying in plain language — "yes", "go ahead", "do it", "approved" — runs the pending card exactly as clicking Approve would, and George then reports what actually happened. With several cards waiting, George asks which one you mean. Replying "no" does not close the card: George will not run it, but it stays waiting until you click Deny. Only Deny turns it into a Declined receipt.
The approval card
When George has something ready, a card titled George wants to: appears in the chat with the steps listed in order, numbered, with "then" between them when there is more than one. There is no time limit: the card waits until you answer it, even if you come back hours later. Under the steps are three buttons:
- Approve — runs the steps, in order, right now.
- Always allow — opens a small menu ("Approve now and skip this confirmation next time for:") listing each action in the card. Pick one, or All of the above, to approve this card and set that action to Always for you, so George runs it without a card next time. Actions that always need a confirmation (archiving, completing work orders, importing a spreadsheet, assigning pools to recurring services) are not offered here; the menu says they "always need a confirmation."
- Deny — closes the card. Nothing is changed.
You do not have to click. With a card waiting, a plain "yes", "go ahead", "do it", or "approved" typed into the chat approves it — George runs it and replies with what happened, and the card becomes the same receipt as if you had clicked Approve. If you change the details in your reply instead ("actually make it Tuesdays"), nothing runs; George prepares a corrected card when you ask. A "no" in the chat only tells George not to run it — click Deny to actually close the card.
Only the person whose conversation it is can approve the card. At the moment you approve, Pool Founder re-checks your role: if your role does not have the permission for a step (say, "Archive and restore customers" for an archive), that step fails rather than running on George's say-so. The same goes for the data: approving checks every step against your records as they are at that moment, so a card that has gone stale (the quote was booked in the meantime, the customer was archived) fails that step with the reason instead of making a duplicate. If one step fails, the steps after it are skipped — nothing later runs on top of a failure.
Receipts: what happened
Once a card is answered it becomes a receipt in the chat so you can always see what George did. The label at the top tells you the outcome:
| Receipt | Meaning |
|---|---|
| Done | Every step ran. Each step shows what was actually done (for example "Archived route Monday A"). |
| Partially done | A step failed part-way ("step 2 failed, 1 step skipped"). Steps before it stayed done; the failed step shows its error; later steps were skipped. |
| Failed | The first step failed. "Nothing was changed." |
| Declined | You clicked Deny. "You declined, so nothing was changed." |
| Expired | Only on cards from before October 22, 2026, when cards had a time limit. Nothing was changed; ask George again for a fresh card. |
| Undone | You clicked Undo. "You reversed this action." |
Clear an old "George needs your OK"
A card George prepared stays waiting until someone answers it, so a request you forgot about keeps its waiting flag: the To do row's button reads George needs your OK (amber), and the chat stays in the list of chats George is busy with. It doesn't clear on its own, and there is no "mark as read". Two ways to clear it:
- From the To do list, without opening the chat: click the ✕ next to George needs your OK ("Dismiss: decline what George is waiting on"). It declines every card waiting in that chat, the same as clicking Deny, so they can never run later. Clicked it by mistake? Click Undo on the "Declined George's request" message that pops up.
- In the chat: click George needs your OK (or open that chat from the George panel) and answer the waiting George wants to: card: Deny if you no longer want the change, Approve if you do. Typing "no" in the chat is not enough: the card keeps waiting until you click Deny.
Once every card in that chat is answered, the button goes back to See George's reply or Ask George. Declining changes nothing in your data. If the to-do itself is the thing you want gone, use the row's ⋯ menu to dismiss it (see your To do list).
Undo within 15 minutes
A Done or Partially done receipt shows an Undo button with the minutes left (for example "Undo 12m"). You have 15 minutes from the moment the steps ran. Undo reverses every step that ran and turns the receipt into Undone; an undo cannot itself be undone.
- Undo is only offered when every step that ran can be reversed automatically. Undoing an archive restores the customer, their locations, and their jobs (or the job, or the route) exactly like the app's own Unarchive button — which means a job that was pulled off its routes by the archive is not put back on them. Re-add it from the Route Planner if you need it scheduled again.
- After 15 minutes the Undo button disappears. From then on, reverse the change the normal way in the app (for example Unarchive on the Customers table with archived customers shown).
- Undo re-checks your permissions the same way Approve does.
George Permissions: Always, Ask, or Never
In the sidebar, go to Settings → George Permissions (or search "George Permissions" in the command palette, ⌘K). The page is headed What George may do. George's actions are grouped by the part of the app they change, and each group is one row you set once: Customers & pools (add or edit customers, service locations, bodies of water, tags and notes), Jobs & visits (add recurring services and work orders, visit reports, water readings), Routes & scheduling (add routes, schedule jobs onto them, skip or move stops), Invoices & payments, Quotes & leads, Texting, email & marketing, Chemicals, parts & inventory (add chemicals and parts, stock), Team & vehicles (add employees and vehicles, schedules, mileage), Templates & company settings, and Memory.
You only see what your role could do yourself. Search (Find an action) finds one action by name, like "tags" or "send invoice".
Each group has a You control with three choices — this is your own setting and only affects your conversations with George:
- Always — George runs the group's actions the moment he decides they are needed, with no card. The chip reads Runs immediately.
- Ask (the default) — George prepares a card and waits for Approve. Chip: Asks first.
- Never — George cannot use these actions at all; he will not even offer them. Chip: Hidden from George.
To make an exception, click the group to open it and set one action's own control. Its Area choice (the default) follows the group; Always, Ask, or Never overrides it for that one action (say, Customers & pools on Always so George adds a customer the moment you ask, but Add notes on Ask). Changes save instantly. Money, deletions, bulk changes and imports show "Always asks first, whatever the area says" instead: nobody can make those skip the card.
The Everyone row (owners and administrators)
Owners and Administrators — anyone whose role has the Set company-wide rules for what George may do without asking permission (Owner and Administrator by default; it can be added to a custom role under Company Settings in the role editor) — also see a second control labelled Everyone on every group, with Default / Ask / Never (inside a group, each action's Everyone control has Area / Ask / Never). This sets the floor for the whole company:
- Default — no company rule; each person's own You setting applies.
- Ask — George must always ask for these actions, company-wide. Anyone who had chosen Always is capped back to Ask; nobody can choose Always while this is set.
- Never — the actions are turned off for everyone at the company. It overrides each person's own setting; their You control is greyed out with a lock icon and the note "Turned off for everyone at your company."
A company rule can only make George more careful, never less: the Everyone control has no Always option, so an owner can never auto-approve an action on someone else's behalf. Order of precedence: an action's own setting beats its group's; then a company Never wins over everything; actions marked "always asks first" always ask; then a person's own Never; then a company Ask; then the person's own Always or Ask.
Importing a spreadsheet in chat
During setup or long after it is finished, you can hand George a customer list without opening the import wizard. In the George chat (the panel opened with Ask George in the top bar, or the George page), click the paperclip button to the left of the message box (Attach a file) and pick a .csv or Excel file (.xlsx, .xlsm, .xlsb, .xls), or drag the file onto the chat and drop it. A chip appears above the message box with the file name and its size in rows and columns; the × next to it removes the file. Then type what you want — for example "import these customers" — and send. The chip stays on your message in the conversation.
- Limits: up to 500 rows and 2 MB. A bigger file is refused right away with an Open Import Wizard link — the wizard handles files of any size.
- The sheet: George works out which column is the name, email, phone, address and so on (the same column matching the wizard uses) and shows the whole import in the chat as a sheet, every row as it will be created, including the service columns (template, technician, day, frequency, rate) George filled in. Click any cell to change it: it works like the wizard's review sheet (paste a column, drag to copy a value down, Cmd+Z to undo). Cells that need a fix are red, and unchecking a row leaves it out. N columns matched above the sheet opens the column matching, with the columns that won't be imported; Full screen opens the same import on the import wizard's review page. On a phone the sheet shows one card per row instead, opening on the rows that need a fix (Needs a fix / All); whichever way it first appears, it stays that way.
- The import: nothing is created until you click Import N of M rows on the sheet. The sheet then reads, for example, "Imported 12 customers and 12 pools", and George carries on from there. You can also tell George "import it": he then prepares an Import spreadsheets step on a "George wants to:" approval card, and nothing is imported until you click Approve (or reply "yes"). That approval is always asked: the card's Always allow menu does not offer it, and the Import spreadsheets row on George Permissions cannot be set to Always. Rows that match an existing customer by email or phone are skipped unless you ask George to attach their pools to the existing customer instead.
- No undo for imports. An import creates many records at once and can add pools to customers you already had, so the receipt has no Undo button. Archive individual customers from the Customers page if something came in wrong.
- Recurring services come along. The chat import reads the same service columns as the wizard — a plan or template name (Template, Service, Plan), Rate, Frequency, Day, and the technician — and creates the recurring service on each pool in the same approval. The template rule is the wizard's: the row's Template value is matched to your recurring services by name (case and filler words like "pool service" ignored); a file with no Template column uses your only template when you have exactly one; otherwise that pool gets no job and the card says "N pools need a service template". Technicians are matched by name to your team (a name nobody on your team answers to leaves the job unassigned), days like "Mon" or "Thursday" set the preferred day, and the Rate column becomes that job's rate (the template default when blank). A file with no service columns at all imports customers and pools only — the card says so — and you add services on the next step.
- Anything George could not resolve is easy to fix before importing: the sheet shows his picks in the service columns (template, technician, day, frequency, rate), and whatever you change there is what gets imported. When George asks one question for a whole column ("one day for all of them?") and you answer, he fills that column and the sheet updates by itself.
Spreadsheet import in chat needs the same access as the wizard (the Create customers permission). Without it — or if Import spreadsheets has been set to Never on George Permissions — attaching a file gets you a link to the import wizard instead of a preview. Attaching a spreadsheet is a web dashboard feature. In the technician mobile app you can only show George photos (the camera button), not spreadsheets or PDFs.
Recurring services (service packages) in chat
- One service or several? During setup, if you have not answered "Do all your pools get the same service, or do you offer several recurring services?", George asks it and prepares a Record one service vs several step.
- Creating recurring services. Say what you sell — "Basic, Full Service and VIP; VIP includes chemicals" — and George prepares one Create several recurring services step with every service: weekly and chemicals billed separately unless you say otherwise, a default price only if you give one, and the charge option from your signup billing answer. Names you already use are refused. The visit checklist is added later on the Services page.
- Giving imported pools their recurring service. Tell George who gets what — "everyone in Palm Springs is VIP", "all the $99 pools are Basic" — and he prepares one Assign pools to recurring services step per service, for example "Put 42 pools on Full Service: … — each keeps its imported rate, day and technician". It works like Add Service in Bulk: up to 200 pools per step, pools that already have service are skipped, and it always asks (it cannot be set to Always). Undo archives the jobs it created.
- Never from the price. George never decides a recurring service from what a pool pays. A rule you state is fine; a hint he spots himself (a recurring service name in the notes) he proposes and waits for you to confirm; with no clear rule he asks.
What George remembers
George keeps short standing facts between conversations so you do not have to repeat yourself: how you bill ("We bill on the 1st of the month"), how you like things done ("Call it a service visit, not a stop"), or a note about one customer ("Dog in the backyard, text before arriving"). Each fact has a scope that decides who George uses it for:
- Company — everyone at your company. George uses it in anyone's chat.
- You (George calls it "just for you") — private to the person who saved it. Nobody else at the company ever sees it, not even in the settings list, unless their role can manage George memories (below).
- Customer — attached to one customer. George uses it when you are on that customer's page.
Three ways to teach George
- Tell him in the chat. "Remember that we bill on the 1st", "from now on call them service visits", "always text the Millers before arriving" — George prepares a "George wants to:" card with a step such as Remember (company): We bill on the 1st. Click Approve (or reply "yes") and the fact is saved. This is the Remember facts row in the Memory group of George Permissions; if it has been set to Never and George only gives you a link to the settings page, use the button below instead.
- The Remember this button. Hover over any of George's replies in the web chat and click the brain icon beside the bubble (Remember this). The dialog is filled in with the text you had selected, or the first sentence of the reply; trim it to the one fact, pick Company (anyone at your company) or Just me (private to you), and click Save. That sends a card into the chat — approve it there.
- Edit the list. Facts that are already saved can be reworded on the George Permissions page (below). There is no "add" button there — new facts come from the chat.
See, edit, or forget a fact
In the sidebar, go to Settings → George Permissions and scroll to the What George remembers card at the bottom. Facts are grouped as Company, You, and Customers; each row shows its scope chip, how it was saved (Saved in chat), and when George last used it. Hover a row for two icon buttons: the pencil (Edit fact) opens the text in place — change it and click Save, or press Enter — and the trash icon (Forget this fact) asks Forget this fact?; click Forget to remove it (or Keep). In the chat, "forget that we bill on the 1st" prepares a Forget: … card that does the same after you approve it, and asking "what do you remember?" lists your facts. A remembered or forgotten fact is undone like any other step with Undo on the receipt within 15 minutes.
The Memory card higher up on the same page lists Remember facts and Forget facts with the usual Always / Ask / Never controls, so you can let George save facts without asking.
Noticed by George. Once a night George rereads your own George chats from the day and keeps your private preferences up to date without being asked: he may add one (the words you use for things, how you like answers), reword one that something newer contradicts, or forget one that is no longer true. Those show here marked Noticed by George and are private to you. He never adds, changes or removes a company-wide fact on his own, and never reads team chats, notes or app activity for this: company facts come only from what someone tells him in a chat, behind an approval card. If a noticed preference is wrong, delete it and he won't add it again. He also picks the suggested questions in a new web chat from what you usually ask him (yours only); with no George chat in 30 days, the standard ones return.
Who can change what
- Anyone can edit or forget a fact they saved themselves.
- Editing or forgetting a fact someone else saved — including seeing other people's private facts in the list — needs the role permission Edit or delete other people's George memories (Roles & permissions, under Company). Owners and Administrators have it by default; Office Managers, Bookkeepers, and Technicians do not. Without it, those rows show no edit or trash buttons.
- George never stores credentials. He refuses passwords, PINs, gate or lock codes, card numbers, and Social Security numbers as a memory; those belong on the service location record on the customer's page, not in his memory.
- A fact is at most 280 characters, and a company can keep up to 200. George reads up to 25 company facts, 10 of your own, and 5 about the customer whose page you are on in each reply.
- On the mobile app George uses your company's and your own facts too, but there is no Remember this button and no memory list there — those are on the web George Permissions page.
Bulk changes
Ask for a change across many records at once — "raise the per-visit rate of every customer on Mike's route by $5", "skip every stop on Sarah's Tuesday route next week, rained out", "add a note to all of the Kennesaw jobs" — and George reads the records, works out which ones the rule covers, and prepares one step per record on a single "George wants to:" card. He tells you the count and the rule he applied ("I've prepared 14 rate changes — every Tuesday customer +5%") so you can check it against the steps before approving.
- The card looks a little different. Above the step list is a George's plan line with his one-sentence intent (for example "Raise every customer on Mike's route by $5 per visit") and a prepared by a script tag, meaning George gathered the records and staged every step in one pass rather than one tool call at a time. The steps underneath are the same kind you see on any card, numbered and in order.
- Bulk changes always ask. Even if you have set that action to Always on George Permissions, a change George prepares across many records still comes as a card you approve. Always only skips the card for a single, direct change. Never and your role's permissions still apply: an action hidden from George cannot be used in bulk either.
- Some bulk changes are one step. Changing how many jobs are billed ("move everyone off external billing to monthly bill ahead") is a single step covering up to 1,000 jobs, so the 50-step limit below does not apply to it.
- At most 50 steps per card. A bulk ask that needs more than 50 changes is not prepared at all — George explains the limit and offers to do it in parts (one route, one day, or one group of customers at a time). He never prepares the first 50 and drops the rest.
- Approve, Deny, and Undo work the same. Approve runs every step in order; the receipt shows what each step did; Undo reverses all of them within the 15-minute window (for actions that support undo).
Nothing in a bulk card has happened yet. Like every card, George only prepares the steps; if his reply ever reads as though the changes were made before you clicked Approve, check the receipt — a pending card means nothing has changed.
What George cannot do (yet)
- Nothing your own role could not do. George only prepares a change that your role could make in the app. Ask for one your role lacks and he says so and names the permission it needs (an owner or admin can add it under Roles & Permissions), instead of preparing a card. A change set to Never on George Permissions is hidden from him.
- Money that can't be undone always asks, one at a time. George can charge a saved card, refund, void an invoice, void a recorded payment, approve or mark a pay run paid, mark tips paid out, add store credit and place a Heritage order, but each of these always shows an approval card (never automatic), one per card, with the exact amount, the customer and the card or order on it. Voiding invoices is the exception to one per card: up to 20 voids can share a card (each line names the invoice, amount and customer), so "these customers don't owe theirs, no emails" is one approval. He never touches your Pool Founder subscription, and he never charges a customer's card for a tip (only the customer does that, on their tip page).
- Mass messages and public posts always ask. George can draft and send a text broadcast or email blast and publish to your Google Business profile, but sending or publishing always shows an approval card with the exact message and how many people it reaches.
- Role changes always ask, and never go past yours. George can create or edit a role and change an employee's roles behind an approval card, but never gives anyone a permission the person approving doesn't have, and never changes the owner's roles or who owns the company.
- Photos come from the chat. Attach a photo in George's chat and he can put it on the record: a visit or one of its tasks, a pool, equipment, a note, an alert, a quote, a service request reply, a chemical, part or restock, a truck problem, repair or receipt, an odometer reading, a payment you record (a photo of the check), a text (as a picture message) or your logo. He can also read what's on a photo or PDF, like a receipt or a test strip, and record it. He can't attach a video to an alert yet, and he can't add a photo from anywhere but this chat.
- Not the technician's visit form. Recording the visit form with photos and GPS, and mileage tracking, happen in the technician app. George can start, pause, resume or skip a stop, pause, finish or reopen your route (with the end odometer), and text a customer that you're on the way.
- No approving on someone else's behalf. A card can only be approved by the person whose conversation it is, and only with the permissions their own role has at that moment.
- No permanent deletes. George archives; he never permanently deletes a customer, job, or route.
Frequently asked questions
How do I undo what George did?
Click Undo on the Done receipt in the chat, within 15 minutes of the change (it shows the minutes left, for example "Undo 12m"). Undo is only offered when every step can be reversed automatically. After 15 minutes, reverse the change the normal way in the app. To see everything George changed, open Settings → Activity and choose George.
I set "Edit job details" to Always. Why did George still show me a card when I asked him to change every customer's rate?
Because it was a bulk change. Always only skips the card for a single, direct change; when George prepares the same action across many records he always puts them on one "George wants to:" card with his plan at the top and a "prepared by a script" tag. Review the steps and click Approve (or reply "yes"). A card holds at most 50 steps — for more, George does it in parts.
Can George set up my service packages and put my imported pools on them?
Yes, with your approval. Tell George what you sell ("Basic, Full Service and VIP; VIP includes chemicals") and he prepares one card that creates every recurring service. After an import, tell him which pools get which recurring service ("everyone in Palm Springs is VIP", "all the $99 pools are Basic") and he prepares one Assign pools to recurring services step per service; each pool keeps its imported rate, day and technician. He never picks a pool's service from a price on his own: a rule you state is fine, anything else he proposes and asks you to confirm first. Assigning always asks and can be undone for 15 minutes.
Can George add a customer for me?
Yes, during setup or any time after. Tell him the name and a phone number or email address and he prepares a "George wants to:" card; click Approve (or reply "yes" in the chat) and the customer is created. Give him the address, service and day too and he prepares the whole sequence — customer, location, job, route — on one card. If George only gives you steps and a link instead, check that "Create customers" is not set to Never on the George Permissions page (yours, or the Everyone row) and that your role has the Create customers permission. Either way, George never creates anything without your approval (unless you have set "Create customers" to Always on the George Permissions page).
Can George make changes from the mobile app?
Yes. Owners and admins can ask George in the technician mobile app (the Ask George button) to make a change, exactly as on the web dashboard. He prepares the same "George wants to:" approval card right in the phone conversation; tap Approve (or reply "yes") and it runs, or tap Decline and nothing changes. The receipt then shows a ✓ or ✗ per step and an Undo button for 15 minutes when the change can be undone. Approving needs a connection.
Can I just tell George "yes" instead of clicking Approve?
Yes. When a "George wants to:" card is waiting, replying "yes", "go ahead", "do it", or "approved" in the chat runs the pending card, the same as clicking Approve — George then tells you what actually happened. Saying "no" in the chat does not close the card; click Deny for that.
Why does George only give me steps instead of an approval card?
One of three reasons. The change is not one George can make (charging or refunding a card, a mass text, a role change, uploading a file — see What George cannot do); the action has been set to Never on George Permissions, by you or company-wide by an owner; or your role does not have the matching permission (George can only prepare what you could do in the app yourself). There is no company-level switch to turn on: every company has George's change abilities, and Ask is already the default. To bring back a hidden action, set its You control back to Ask, or ask an owner to set the Everyone control back to Default.
How do I stop George from asking me every time?
Most everyday changes don't ask at all: in Auto mode (the default, the switch under the message box) a change you can undo just happens, with Undo on its card. For the ones that still ask, two ways. On the approval card, click Always allow and pick the action (or All of the above) — that approves the card and sets the action to Always for you. Or go to sidebar → Settings → George Permissions and set the group's You control to Always (or open the group and set just that action). Archiving, completing work orders, and importing a spreadsheet can never be set to Always; they always ask. A company-wide Ask set by an owner also keeps everyone at Ask.
Can I turn George's changes off completely for my team?
Yes, if you are an Owner or Administrator (or your role has "Set company-wide rules for what George may do without asking"). On George Permissions, set a group's (or one action's) Everyone control to Never; that hides it from George for everyone at the company and greys out each person's own setting with a lock. Set Everyone to Ask if you just want to make sure nobody can auto-approve it.
How do I undo what George did?
Click Undo on the Done or Partially done receipt in the chat. It shows the minutes left; you have 15 minutes from when the steps ran, and it reverses every step that ran. George saves a copy of each record before a step changes it, so Undo puts back everything the card changed (a rate, a billing mode and billing day, a schedule, a note), even when the receipt only lists part of it; you do not need to know or re-enter the old values. George cannot click Undo for you: you click it on the receipt. Undo is refused if someone has changed one of those records since, and it is not offered for a card that emailed or texted someone, charged or synced with Stripe or QuickBooks, deleted something, or merged customers. After that, reverse it the normal way in the app (for example Unarchive on the Customers table with archived customers shown). Undoing an archive restores the records but does not put the job back on its routes.
What happens if I do not answer the card?
Nothing happens: it keeps waiting, with no time limit, until you click Approve or Deny (or reply "yes"). When you approve later, every step is checked against your data as it is then; if something changed in the meantime (the quote was already booked, the customer was archived), that step fails with the reason and nothing is duplicated.
Can I import a spreadsheet of customers by giving it to George?
Yes, whether or not setup is finished. Click the paperclip (Attach a file) next to the message box in the George chat, pick a .csv or Excel file up to 500 rows / 2 MB, and tell George to import it. He shows the import as a sheet right in the chat (every row, editable; cards on a phone), and the customers are created only when you click Import on that sheet, or approve the card George prepares if you tell him to import it (that one always asks and cannot be set to Always allow). Bigger files, or a user without the Create customers permission, get a link to the import wizard instead. Imports cannot be undone from the receipt.
Can George remember things between chats?
Yes. Say "remember that we bill on the 1st" and George prepares a card to save it; approve it and he uses that fact in every later conversation. You can also hover any of his replies and click the brain icon (Remember this) to save a line from it as a Company fact (everyone) or Just me (private). He refuses to store passwords, PINs, card numbers, Social Security numbers, or other credentials.
Does George learn from my chats on his own?
Only your own private preferences, and only from your own George chats. Once a night he rereads the day's chats you had with him and adds a preference worth keeping (what you call things, how you like answers), rewords one that something newer contradicts, or forgets one that's no longer true. They appear in the What George remembers card (Settings → George Permissions) marked Noticed by George, private to you; delete one that's wrong and he won't add it again. He never adds or changes a company-wide fact on his own, and never reads team chats, staff notes, direct messages, invoice notes or app activity for this: a company fact is saved only when someone tells him in a chat and approves the card. He makes at most 15 changes a night and never saves numbers he can look up, anything about one customer, or credentials.
Where do I see or delete what George remembers?
Sidebar → Settings → George Permissions, in the What George remembers card at the bottom. Hover a fact for the pencil (Edit fact) or the trash icon (Forget this fact, then Forget to confirm). You can always edit or forget your own facts; other people's need the "Edit or delete other people's George memories" permission, which Owners and Administrators have by default. In the chat, "forget that…" does the same behind an approval card.
Can George move a job or skip a visit for me?
Yes, from the web dashboard. Ask in plain words — "move the Smith visit to Thursday", "give Corey's Tuesday route to Maria", "skip the Jones pool this week" — and George prepares the change on a "George wants to:" approval card; nothing moves until you click Approve (or reply "yes"), unless that action is set to Always on George Permissions. A change across many stops always asks. Most changes can be undone from the receipt for 15 minutes; one that emailed or texted someone, charged, deleted, or started background work says it can't be undone — ask George to move it back instead. The same works from George in the technician mobile app: the card appears in the phone conversation with Approve and Decline. To do it yourself, see Transfer and move jobs and Pause, skip, or archive jobs.