[All use cases](https://missblue.dev/use-cases) iMessage for plumbers # Turn the leak inquiry into a booked call. *Reply before the next plumber does.* Give dispatchers and technicians one business iMessage line for fast, two-way customer communication. Ask for the details that matter, collect photos in the thread, coordinate arrival, and follow up on estimates from the Miss Blue inbox or your existing software. [Start with Miss Blue](https://missblue.dev/signup) [See sale pricing](https://missblue.dev/pricing) **80%** higher response rates **37%** more attributed revenue Internal observations reported by participating Miss Blue beta customers comparing their iMessage and SMS outreach. Results vary by audience, timing, message, use case, and attribution method. [Read the research.](https://missblue.dev/imessage-response-rate-study) Where the conversation breaks ## Plumbing customers contact whoever can make the problem feel controlled. The first useful response is not a generic auto-reply. It confirms that someone is listening, gathers just enough context to route the call, and sets an honest expectation for what happens next. 01 ### Urgency is hard to describe A customer may say only that a pipe is leaking or a drain is blocked. A short guided exchange can ask whether water is shut off, whether damage is active, and whether a photo would help dispatch prepare. 02 ### Phone tag delays booking Customers at work or dealing with a noisy emergency may not answer a call. A familiar thread gives them a low-friction way to confirm the address, time window, and access details. 03 ### Estimate follow-up gets forgotten After the immediate visit, repair and replacement estimates can sit unanswered. A useful follow-up should reference the actual work discussed and offer a clear path to ask a question or schedule. High-value workflows ## Use iMessage where a real answer moves the work forward. Each workflow begins with a signal the customer recognizes, keeps the next ask small, and gives a person a clear place to take over. 01 Lead intake ### New service request Acknowledge the request, identify the plumbing company, collect the service address and problem type, and route emergencies according to an operator-approved policy. 1. 1Confirm the requested service 2. 2Ask for address and urgency 3. 3Invite a photo when useful 4. 4Hand off to dispatch 02 Dispatch coordination ### Appointment and arrival Confirm the time window, send an on-the-way update from the business line, and give the customer an easy reply path if access or timing changes. 1. 1Confirm the visit window 2. 2Share technician context 3. 3Send a useful arrival update 4. 4Capture reschedule replies 03 Revenue recovery ### Estimate follow-up Reference the inspected issue and proposed next step without turning the message into a generic promotion. Stop the sequence when the customer replies or declines. 1. 1Use the estimate identifier 2. 2Summarize the next decision 3. 3Offer a scheduling path 4. 4Record the outcome 04 Customer retention ### Post-job care Check that the repair is holding, answer a practical care question, and ask for a review only after the service outcome is known. 1. 1Confirm the job outcome 2. 2Share relevant care guidance 3. 3Resolve issues first 4. 4Request a review when earned Start without code ## One line. *Two ways to work.* Use Miss Blue as the complete conversation platform, connect it to software, or let the same workflow move between both. For the team ### Message Center Add contacts, see shared history, assign the next reply, and continue conversations directly from the browser. [Explore Message Center](https://missblue.dev/features/message-center) For the workflow ### iMessage API Send from granted business numbers, receive real-time events, preserve identifiers, and connect a human handoff. [Explore the API](https://missblue.dev/imessage-api) Implementation playbook ## Build the operating rules before increasing volume. The strongest industry page is not a list of message templates. It is a recoverable process for identity, ownership, consent, routing, and measurement. 1. 01 ### Separate emergency from routine Create clear routing rules for active flooding, no-water situations, gas-related concerns, routine maintenance, estimates, and after-hours requests. 2. 02 ### Keep the dispatcher in control Automation can collect initial facts, but a person should own promises about availability, diagnosis, pricing, and emergency response. 3. 03 ### Use photos deliberately Ask only when an image can improve routing or preparation. Do not imply that a photo replaces an on-site diagnosis. 4. 04 ### Match the job record Store the customer, address, appointment, technician, estimate, and conversation identifiers separately so updates reach the right household. 5. 05 ### Measure booked work Track qualified replies, booked appointments, show rate, estimate acceptance, repeat service, opt-outs, and dispatcher workload. CRM and automation ## Connect dispatch signals without replacing dispatch judgment. Start from an inbound form, missed call, requested quote, appointment change, or approved follow-up in your CRM. Miss Blue can send the conversation, report reply state, and route the thread to the team inbox while your field-service system remains the source of truth for the job. [Browse every integration](https://missblue.dev/integrations) [GoHighLevel](https://missblue.dev/integrations/gohighlevel) [HubSpot](https://missblue.dev/integrations/hubspot) [Zapier](https://missblue.dev/integrations/zapier) [Make](https://missblue.dev/integrations/make) Measure the conversation ## Count outcomes—not bubbles. Compare the same eligible audience, time window, and attribution method. Treat Miss Blue's beta observations as a hypothesis for your own controlled rollout, not a guaranteed result. 01 ### Inquiry-to-booking time How long it takes to turn a qualified request into an appointment. 02 ### Appointment confirmation Customers who confirm or reschedule before dispatch. 03 ### Estimate recovery Open estimates that return to a useful conversation. 04 ### Repeat-service rate Customers who come back for maintenance or a future issue. Trust and consent ## A blue bubble does not replace permission. Miss Blue is built for expected, relevant, two-way conversations. Your business remains responsible for consent, identity, opt-outs, quiet hours, recordkeeping, and every law or professional rule that applies to the workflow. - Do not present automated text as emergency dispatch unless a qualified person is actually monitoring it. - Use explicit, expected follow-up and honor STOP or other opt-out requests. - Avoid diagnosing safety-critical plumbing or gas conditions through automation. - Keep payment details, access credentials, and other sensitive customer information out of routine text workflows. Frequently asked questions ## Questions about iMessage for plumbers. Can customers send photos to the plumbing company?+ Miss Blue supports media in the conversation workflow. Ask for a photo only when it helps dispatch understand the request, and make clear that it does not replace an on-site assessment. Can dispatch use Miss Blue without developers?+ Yes. The Message Center lets dispatchers add contacts, manage threads, and reply from the business line. API access is included when you want to connect forms, CRM stages, or field-service events. Is Miss Blue an emergency answering service?+ No. Miss Blue is a messaging platform. Your company must define monitoring hours, emergency language, escalation, and the qualified people responsible for urgent requests. Can technicians and office staff see the same conversation?+ Authorized teammates can share conversation context in the Message Center. Access should be limited to the numbers and workflows each person needs. Explore related industries ## More ways to put the conversation to work. [HVAC](https://missblue.dev/imessage-for-hvac) [Roofing](https://missblue.dev/imessage-for-roofers) [Home services](https://missblue.dev/imessage-for-home-services) [Maid services](https://missblue.dev/imessage-for-maid-services) Start the first workflow ## Use the inbox. Connect the API. *Keep the reply.* [Create your account](https://missblue.dev/signup) [Lock in 50% off](https://missblue.dev/pricing)