Private operational texts

Private texts live beside an inquiry’s email conversation. Open Conversations → Private operational texts to review phone permission, prepare a message, read verified replies and inspect original delivery receipts. A saved phone number, guest wedding opt-in or vendor schedule preference does not authorize this private business conversation.

Invite and verify a recipient

A current workspace owner or administrator can prepare an expiring permission link for the inquiry’s recorded US phone and a configured workspace sender. Copy the link to share through a channel you already use with the person. Preparing it does not send an email or text.

The recipient sees the sender, operational purpose and a masked phone, chooses a timezone and delivery window within 9 a.m.–8 p.m., and explicitly agrees to the notice. They then send the displayed WBCRM verification code from their phone to the sender number. Only a verified provider event matching that current, unexpired challenge activates permission. The page opens only text preferences; it does not expose the private conversation.

The recipient can withdraw on that page or send STOP to the sender. START alone never enrolls them again. After a carrier stop, a fresh notice and phone challenge are required. Replacing a permission link, changing the phone, archiving or merging the inquiry invalidates previous authority. Restoring the inquiry or changing a phone back does not revive it. Routine pipeline stage changes preserve phone permission.

Review, schedule and queue

Choose a current verified permission, write the text and optionally select a local send time with its IANA timezone. Skipped or repeated daylight-saving times require another choice. The review includes the complete message, sender, destination, private reply code, STOP instruction, encoding, segments, saved integer segment price and maximum USD usage cost. Quiet hours use the recipient’s chosen timezone. No urgency setting bypasses them.

Review the exact rendered message and approve it before queueing. A review expires after 15 minutes; a queued message expires within 24 hours of its requested time or when its permission expires, whichever comes first. The worker checks the current sender, recipient, permission, approving administrator, feature pause and owner-approved spending budget before an actual provider attempt. Missing setup or a paused budget produces a visible hold.

Accepted delivery is a provider receipt, not proof that a person read the message. If an attempted request loses its response, the original attempt remains uncertain and is never automatically retransmitted. A known provider message ID can be reconciled against its original account. An attempt without a known ID remains for review. Stopping further delivery cannot recall an already accepted text.

Replies and shared phone numbers

The recipient can include the WC code from the text to identify the exact private conversation. An ordinary reply without a code routes only when the verified sender and phone have one safe context. When another inquiry, guest household or coordination recipient shares the number, an explicit code is required. Ambiguous replies stay in the workspace administrator’s unassigned queue; they are not guessed, copied to several conversations or attached to the newest inquiry.

A verified CRM reply updates the private conversation and stops applicable follow-ups. Message deliveries, replies, permission history and unassigned replies have independent history pages. Full workspace staff may read the private conversation; only current owners and administrators can prepare permission links, review paid sends or read the workspace unassigned queue. Permission links are not included in staff projections.

Workflow texts

The workflow builder supports Draft private text and Review and send private text. Simulation can show sample phone, sender, segment and price facts without creating permission, spending, messages or provider calls. Existing email workflow versions retain their original format.

A draft step creates private work for review. A send step pauses each run for an administrator to review its exact phone permission, saved content, sender, delivery window and maximum cost. Publishing a workflow is not SMS consent or spending authorization. After approval, the run waits for the original receipt before continuing. Reply, closed-lead, booking, payment and pause policies are checked again. Uncertain delivery cannot be skipped or retried into another text.

Setup and current limits

Development rehearsals use synthetic recipients, signatures and provider adapters. Real sender registration, carrier behavior, production webhook configuration, pricing and end-to-end provider delivery remain coordinated activation tasks. This workflow handles operational US text messages for the owning workspace’s primary inquiry phone. It does not add MMS, bulk marketing, international sending, automatic consent from contact imports or a legal certification of consent.