50 ways businesses use iMessage, with real workflows

What makes a good iMessage use case?

A good ZeroSettle use case is a one-to-one conversation that the customer started or agreed to, where the reply matters and most recipients use iPhone. The 50 pages below share four traits:

• One to one. Each person hears from one number in a private thread. ZeroSettle has no group chats.
• Customer-started or consented. The person texted first or opted in.
• A reply does something. A YES books the slot, a 👍 tapback confirms, a photo opens a work order.
• Mostly iPhone recipients. There is no SMS fallback, so other phones need another channel.

Who sends the first message sets the limit

ZeroSettle caps how many new people each number starts conversations with, so who sends first matters. In the docs' words, "A 'new contact' is a handle the line delivers a text, voice message, or photo to first; reactions, typing, profile shares, and failed sends never count. Anyone who texted the line first is never limited, and neither is an ongoing conversation." The caps keep a number out of Apple's spam filters.

Photos and voice messages go only to contacts who have replied; to someone who never has, the API answers 403 attachment_before_reply, so a first message is always text.

Volume has a second ceiling: one number sends one message at a time, normally 2–5 seconds each, so 300 messages into existing threads take about 10–25 minutes.

What a first text needs: no link, and consent

A first text from your number should carry no link and should go only to someone who agreed to hear from you. An iPhone shows a link from an unknown sender as plain text until the person replies or saves your number, so many pages below open with a link-free question, and getting customers to text you first avoids the problem.

Consent, as ZeroSettle's docs define it, means four things:

1. The person gave you their number for this purpose, and you can show the record.
2. Your first message says who you are.
3. You honor STOP immediately; ZeroSettle enforces it across your account too.
4. Nothing promotional goes out before 8 am or after 9 pm in the recipient's time zone.

In the US, the docs add, marketing texts generally need written consent; the FCC's TCPA rules are at 47 CFR 64.1200, and the TCPA consent guide covers them. Rules vary by place and purpose. This isn't legal advice.

Use cases by job

The 50 ZeroSettle use cases fall into 13 jobs. Each page has the workflow, an illustrative thread, the limit math and its failure modes.

Customer support

• Tenant maintenance requests: tenants text a photo of the problem; your webhook opens the work order and confirms with a 👍 tapback.
• Hotel guest messaging: one number for the stay, with a hosted AI concierge for check-in, parking and Wi-Fi questions.
• Event attendee help line: a number on every badge, answered by the hosted AI agent from your agenda and room map.
• Insurance claim photos: policyholders text damage photos and your webhook files them to the claim, with storm-day reply math.
• "Where is my order?": your webhook looks up the order in Shopify and replies with tracking, which the hosted agent alone can't do.
• Support in Slack or a help desk: a relay you run posts each text to Slack; replies go back through the API.

Scheduling

• Appointment reminders: clients confirm with a 👍 tapback that reaches your webhook as reaction.received.
• Cancellation waitlist: offer a freed slot to one waitlisted client at a time and book the first YES.
• Restaurant waitlist: guests join from a QR code at the host stand and get a "table ready" text from the console.
• Shift coverage: offer a call-out shift to staff one by one and give it to the first YES.

Customer updates

• Technician on-the-way texts: the arrival time, then the tech's photo in a captioned bubble once the customer has replied, with replies passed to the tech.
• Auto repair approvals: a photo of the worn part with the price once the customer has replied, and their YES logged from the webhook.
• Pet care updates: visit photos, a voice-message discharge summary and a pickup text in one thread.
• Tutoring parent updates: recaps and worksheet photos from a program number, so tutors' numbers stay private.
• Proof-of-delivery photos: a captioned drop-off photo to buyers who have replied in the thread, and when a photo loses its GPS data.

Lead capture

• Text-a-photo quotes: customers text a photo of the job; an estimator replies with a price range and booking link.
• Law firm intake: "Text us" on ads, after-hours intake questions from the hosted agent, documents on a secure upload link.

Sales follow-up

• Car dealership leads: a link-free question about the exact vehicle, then lot photos and a voice walkaround once the lead replies.
• Fitness studio intro offers: a text from the instructor after class, then a voice note and the membership link once the client replies.
• Admissions follow-up: the hosted agent answers tuition, financing and start-date questions from prospective students.
• Real estate leads: yard-sign QR codes and a fast opener from a business number, then a voice walkthrough once they reply.
• Abandoned checkout: one link-free question to opted-in shoppers, kept to high-value carts on Pro.
• Retail clienteling: stylists text new arrivals from store-owned numbers, so history stays when staff leave.
• AI SDR for demo requests: the hosted agent texts each demo request within seconds and sends your booking link.

Retention

• Donor thank-you: a thank-you text to each first-time donor who opted in, then a voice message from your executive director and an impact photo once they reply.
• Skip, swap or reorder: ask "keep, skip or swap?" before each renewal and act on the reply.
• Paywall abandonment: three texts seconds after an opted-in user leaves the paywall, offer last.
• Trial-ending and renewal reminders: YES, PAUSE or CANCEL replies mapped to your billing API.
• Failed payment recovery: a link-free heads-up, then the billing link once the customer says yes.
• Cancel-flow save: an optional "Text the founder" step; the customer texts first, so it costs no new contact.
• Win back lapsed subscribers: the hosted agent texts opted-in lapsed customers, within the daily allowance.
• Founder-led SaaS onboarding: one personal question to each new trial user, and a nudge when they stall.

Commerce

• Back-in-stock alerts: fans text for a sold-out size and get a photo and link on restock.
• Text-to-buy: answer a product question and send a Stripe payment link in the thread.

AI agent

Two of these run on ZeroSettle's hosted AI agent (Beta) with no server; two use your own model.

• AI receptionist: answers every text, day or night, from a business context you write.
• Creator "text me" line: a link-in-bio number answered in your voice, working toward your checkout link.
• Give your AI agent a number: your webhook calls your own model with your own keys.
• Personal AI assistant: allowlist your own handle and poll from a home machine, with no public server.

Sign-in

• Sign in with iMessage: users tap Send on a prefilled code and your auth provider issues the session.
• Phone verification without outbound SMS: users text you the code, so there is nothing for SMS pumping to exploit.

Operations

• Receipts to your bookkeeper: clients text receipt photos; your webhook runs OCR and confirms with a tapback.
• HubSpot or Salesforce logging: a service you run logs each message and sends only when consent is true.
• Zapier, n8n or Make: verify the signature over the raw body, then reply with one HTTP request.
• On-call alerts: a 👍 tapback acknowledges; silence escalates. Not your only pager.
• Field voice reports: technicians' voice memos, transcribed into Jobber, ServiceTitan or a spreadsheet.

Reviews and feedback

• Google review requests: a question first, then the review link to everyone who replies, with no review gating.
• Tapback feedback surveys: one question after a ticket, scored from the 👍 or 👎 tapback.

Engagement

• Coaching check-ins: daily tapback answers and meal photos, with voice notes back from the coach.
• Voice lessons for language apps: spoken lessons as voice bubbles, and why learners shouldn't type "stop".

Recruiting

• Text-to-apply hiring: applicants text JOBS, and a hosted AI screener asks everyone the same questions.

Use cases by industry

Each of the 50 ZeroSettle use cases appears once more below, under the kind of business its page was written for; subscription apps and SaaS have the most, with nine.

When ZeroSettle is not a fit: what iMessage is not for

ZeroSettle is the wrong tool when a job needs reach, volume or formats a one-to-one iMessage number lacks:

• High-volume marketing or purchased lists. ZeroSettle's terms prohibit high-volume marketing and unsolicited messaging, and the people on a purchased list never gave your business their number. Use an SMS marketing platform for consented campaigns at scale.
• Android and other non-Apple phones. There is no SMS fallback yet (it is on the roadmap), and a "Text us" link opens the SMS app on Android, so keep email or chat for those customers. Apple's support page describes iMessage as going to another iPhone or Apple device, and RCS or SMS/MMS as also reaching other phones, so use an SMS or RCS provider, or WhatsApp; see iMessage vs SMS vs RCS vs WhatsApp.
• Group chats. Conversations are one-to-one; groups are on the roadmap.
• Video or files. Only photos (5 MB) and voice messages (6 MB) send; share a link once the customer has replied.
• Protected health information. Not allowed without a signed Business Associate Agreement (BAA) with ZeroSettle; keep it in your patient portal.
• Alerts that need a contractual SLA. ZeroSettle's homepage shows "99.9% uptime", but no SLA is published and the terms promise no uninterrupted service, so keep a second channel for anything critical.
• Chats that start from Apple Maps, Safari or Search. Apple says customers start those from Maps, Safari, Siri and Search and from participating businesses' websites and apps; that is Apple Messages for Business, which ZeroSettle is not part of. See Apple Messages for Business vs an iMessage number.

The iMessage API comparisons put the alternatives side by side.

How to start

Start on Pro if one number and 5 new contacts a day cover your use case (people who text you first are unlimited); book a Growth demo if you need several numbers working as one and more new contacts. What is ZeroSettle? and the how-it-works explainers cover the basics, and the plans on the ZeroSettle homepage list what each includes.

1. Press Get started and sign in with your phone number. A number is set aside for you while you finish.
2. Say what the number is for: sign in with iMessage, branded messages or an AI agent. That claims it.
3. Set your brand name and photo, and text yourself a test (you can skip it).
4. Subscribe. The console and API open once the subscription is active; a number not paid for within 30 minutes is released.

Numbers can sell out: if all numbers are taken, you can join the waitlist.

To have Claude Code do the setup, add ZeroSettle's MCP connector, which signs you up, mints your server's API key, and registers and tests your webhook. It is a setup tool, not a way to message customers:

claude mcp add --transport http zerosettle https://portal.zerosettle.io/mcp

No server? Write a business context and switch on the hosted AI agent (Beta) in the console's Messaging tab. ZeroSettle pricing covers AI credit packs and the 30-day money-back guarantee; the API docs have each recipe's code.