One manager.
The whole operation.
Piquup answers every call, text, and email on your number, books real jobs on your real calendar, routes what it can't answer to the teammate who can, and remembers every customer it has ever talked to. Here's the whole job, up close.
Every way in lands in one place.
A call, a text, the form on your website, an email, a breakdown at 9:42 PM. Each one is handled, or handed to the person who can, and every one of them lands on the same board.
Answered on the number they already have.
Piquup picks up every call on your existing number, day or night, no hold and no voicemail. The same brain runs your texting and reads your inbox. It reads your Google Calendar live, holds the slot while the caller is still talking, and books the length the job actually takes.
- Calls answered around the clock, on the number you already have now
- Two-way SMS: same thread, same memory now
- Email triage with drafts you approve before they send building
- Booked before they hang up, on your real calendar now
Calls, texts now · Booking now · Email, website chat building
Work that arrives late reaches a human who isn't you.
A breakdown on a Friday night is a ticket, not a voicemail. Piquup tells you, then offers the job to the nearest technician who can take it: your own crew first, then the network you approve, by text and then by call. The first yes wins, the customer gets an estimated arrival and a map pin, and if nobody takes it, Piquup calls you.
Dispatch building
Every department gets its own line. Every teammate gets a seat.
Estimates, service, and billing each get a line with its own voice and instructions. An invite link is the whole onboarding: each teammate claims a seat and sees their own queue, not the whole firehose. A hard question goes to the seat that would know.
Seats, lines, invite links now
Same customer. Every channel. One record.
Every call, text, ticket, and email writes to one record, so nobody repeats themselves and the manager knows who is on the line before the first hello.
It remembers everyone you've ever talked to.
Callers are recognized by phone number. Voice, email, and SMS all write to one record, so your regulars get greeted like regulars, because the manager actually knows them. Your knowledge base lives on the same record: services, hours, policies, the questions to ask per service.
Illustrative records. Names and places are invented; no outcome is a claim.
Customer memory now · Knowledge base now
A ticket is a record too.
The breakdown from Friday night lives on the same record as the customer who called it in: what was wrong, where, who took it, and every message in between. When the work is done, nothing has to be typed up after.
Tickets on the record building
Money in, matched to the customer who paid it.
The bank read is a read: Piquup sees deposits and matches each one to the customer and the job, so money in has context the day it arrives. Payments, payroll, taxes, and the books sit on that same record when they land. None of it is here yet, and the marks say so.
It notices what you wouldn't have looked for.
Every call, text, and email already wrote itself to one record, so the history is there before anyone asks for a report. Piquup reads it back in plain sentences, with the numbers that back them: what changed, what is worth acting on, what pays.
Plain English, real numbers, no chart.
Which day slipped, which customers went quiet, which hours book and which do not. Not a dashboard to interpret: sentences about your own week, each one tied to the records behind it. This is the part of the manager that is not built yet, and it says so.
Deep tissue is down 22% on Tuesdays. It was your best day in June.
Three customers quiet for 60 days are worth $4,100 between them.
Saturday books 2.4x Wednesday. You staff them the same.
Money in: $2,840 cleared, matched to 3 customers. next
Illustrative numbers, for a studio that does not exist.
Weekly insight next
It writes the next move. You say yes.
A drafted reply, a callback, a reactivation text, a review request. Each one is queued with the reason it exists, and nothing sends in your name until you approve it.
Drafted, queued, waiting on you.
Email replies are drafted from the thread and the record. Callbacks are placed on your say-so, inside business hours, and logged like any other call. Reactivation and review outreach come later, and are marked that way.
Illustrative queue. Nothing here sends itself.
Email replies building · Callbacks building · Reactivation, reviews next
It doesn't take a message. It gets an answer.
When a question needs a human, Piquup texts the teammate who'd know and keeps hold of the customer's thread while it waits. One line back is all the team owes. The reply comes back as a finished answer from your business, and the whole exchange is logged.
Questions to the right teammate now
It guards your attention.
You define what is urgent, and only that reaches your phone. Everything else lands in the dashboard, summarized, and booking reminders go out to customers on their own.
Owner pings, reminders now
Ask your business a question.
Connect from Claude Code, Codex, or Cursor, sign in with your Piquup account, and the agent and the dashboard become two windows onto one business. Same question, same answer, either door.
Works from Claude Code, Codex, or Cursor. An illustrative session.
What should I do first today?
Two bookings today. One question is waiting on Marcus; it is on his phone. Three new customers since Monday. Start with the adjuster's email: the draft is ready.
Illustrative session. Same brain, pointed at you.
Your agent (Claude Code, Codex, Cursor) now · Dashboard chat next
Day zero, when it lands.
Your customers' conversations stay your customers' conversations.
Nothing you or your customers say trains shared models. It's encrypted in transit and at rest, and every transcript and record exports whenever you ask.
Put a manager on it.
Piquup is open by waitlist. Join for early access, or hear it first: (470) 695-9004 answers as a Piquup agent.