Operations
If that email is registered, a reset link is on its way.
What Geoff can send a customer when he finishes a visit. Each message has a few wordings, and one is picked per visit so they do not repeat.
Finds appointments that have no Google Calendar event and writes them. New bookings are handled automatically. Use this only when something is missing from the calendar, or to fill in past work. Safe to re-run: an appointment that already has an event is left alone.
What each service asks a customer after they book. Access questions (gate code, parking, pets) apply to every service. Job questions are specific to that service. Turn Access off to send no intake at all.
Turn this on for a service that sometimes waits on a part being ordered or picked up. When it is on, PoolCrew asks whether the job is waiting on a part, with No part needed as the first answer. When it is off, the question is never asked. Off is the default for anything new.
The bell in the top bar. Read notifications are cleaned up automatically; unread ones are always kept.
What PoolCrew asks Geoff to do on a visit. Switch a step off and every technician skips it. Changes reach PoolCrew the next time it opens.
Short heads-ups PoolCrew shows at a stop, based on the forecast for that pool's address. Switch one off and nobody sees it. Changes reach PoolCrew the next time it opens.
Every few days we pick photos from recent jobs that passed the privacy check and put them in a task for you. You edit the label, add the photo in Google yourself and tap Posted. Nothing is posted for you. Repairs and one-time jobs are preferred so the profile shows the breadth of our work.
What each AI model costs, in dollars per million tokens. The Dashboard's AI cost card multiplies what every AI call used by these prices, so it is an estimate and the provider's invoice is the final word. Check these against each provider's pricing page when a price changes or a new model is added.
When you send a “Let them confirm the day” link for today, these decide how late today can still be picked. After the cutoff, today drops off the customer's list and the next open day is offered instead. Set each one to the latest you'd still want to send someone out that day. Changing these affects links already sent, because the list is built when the customer taps, not when you send.
When a customer texts in and the thread needs a person, we send you a text. After-hours alerts always send and can't be turned off, since that's the case nobody is watching the Inbox for. The switch below only controls whether you also get a text during business hours, when the Inbox is already dinging on its own. We only text you once per conversation within the cooldown set below, so a customer sending several messages in a row won't blow up your phone.
How automated texts are paced. Shown so you can see what the system is doing · these are not editable here. Tap an info icon for what each one means.
What we text customers, automatically.
A technician can text a customer a pay link for anything switched on here. The price always comes from the service's catalog price at the moment the customer taps the link, so a price change applies to links already sent. Switching one off kills links already sitting in a customer's texts. Every change here is logged.
Cold campaign contacts. Nobody here has asked to join. They become a pending approval the moment they verify their email.
Wave 0 is 240 recipients. Judge it at day 26, once all five stages have landed. Reading it earlier reads a partial sequence.
Go to wave 1 if all of these hold. Hard bounces under 2%. Unsubscribes under 1.5%. Spam complaints under 0.1% in Postmaster Tools. Opens above 30%. And at least 2 activations, or 4 genuine replies.
Stop and rethink if any of these. Opens below 25%, which is a deliverability or subject-line failure and you need to know which before resending anything. Unsubscribes above 2.5%. Complaints above 0.3%. Or zero activations together with fewer than 2 replies.
The one that looks like failure and is not. Zero activations with 3 or more real replies is a landing-page problem, not a list problem. Fix the page and re-run on 240 fresh names rather than burning wave 1.
What to expect if it is working. Wave 0: opens 35 to 45%, clicks 2 to 4%, 2 to 5 activations. Across the full 1,514: 15 to 30 agents activate. Roughly half of those ever send a client, at 2 to 4 inspections each per year. First booked inspection lands 3 to 8 weeks after wave 0 starts, because an agent activates and then waits for a pool listing. Deliverability is readable in 5 days, engagement in about 3 weeks.
Do not change the copy mid-wave. The activation rate is the one number wave 0 buys you, and editing partway through spends it.
These are the live numbers the sender reads before every batch. A change here takes effect on the next run; nothing already sent is affected. Everyone on the list receives all five emails in order. Anyone who replies, signs up, unsubscribes or bounces stops receiving them straight away.
Send yourself a copy of the campaign at each provider, open it, and record where it landed. Re-checking on the same day corrects the earlier entry rather than adding a second one.
Each price is the customer's all-in price for that choice, labor included. Labor is not a separate line here, so nobody wonders whether it is optional too.
Checked means we already have this. Uncheck anything wrong or missing · we'll text the customer about whatever's left unchecked.
The card goes straight into Stripe's form below, never into ours.
The card goes straight into Stripe's form below. No payment link is texted to the customer.