Rules before actions
Availability, policy, consent, and access checks stay deterministic.
Bookings in the conversations customers already use
Turn customer messages into confirmed appointments—with your rules in control.
WAHNX is being built for appointment-based businesses that want a clearer way to answer approved FAQs, offer valid times, and manage booking or rescheduling requests through connected messaging channels.
AI helps understand the request. Structured workflows validate availability, policy, and customer confirmation before anything changes.
Illustrative workflow — sample data
Try a structured booking flow
Customer request
AI interprets intent and can answer from approved FAQ content. The structured workflow validates every booking action.
01
Request understood
Required details are organized for validation.
03
Confirm explicitly
Final rules and availability are rechecked before a booking is committed.
Choose one of the sample times to continue.
This preview is not connected to a live booking, payment, calendar, or customer system.
Confirmation before commitment
Customers see the final appointment details before a booking changes.
A traceable operating record
High-impact owner actions require approval and an audit trail.
The everyday friction
A busy day should not scramble the schedule.
Customer messaging is convenient, but unstructured appointment requests can create extra work for the people running the business.
Booking requests arrive at inconvenient times
A new appointment request can be easy to miss while a team is with customers, travelling, or away from the phone.
Appointment details become fragmented
Dates, services, policies, and follow-up messages can end up spread across chats and handwritten notes.
The same questions keep returning
Hours, directions, service details, and booking policies add repetitive work when every response is manual.
A controlled path to confirmation
Conversation on the outside. State machine underneath.
The customer gets a natural exchange. The business gets a predictable sequence with required details, validation, confirmation, and an auditable record.
01
Understand the request
AI can identify booking intent or answer from approved FAQ information. If a request is unclear, it asks a focused question or hands off.
02
Collect and validate details
The workflow checks the business context, service, required fields, timezone, and booking policy before presenting any choice.
03
Offer valid times
Only available options are shown. A selected time can be held briefly while the customer reviews the final appointment details.
04
Ask for explicit confirmation
The customer confirms the service, date, time, timezone, and business. The workflow rechecks availability before it commits.
05
Save, confirm, and queue handoffs
The booking record is saved first. Customer confirmation, reminders, and secondary calendar work are queued only afterward.
A focused product boundary
Built around appointments, not vague automation.
Core booking behavior is separated from the channel and lifecycle work that still depends on provider permissions and staged rollout.
01Core workflow
Book
Structured appointment booking
Collect required details, offer valid slots, place a short hold, and confirm only after a final policy and availability check.
Plan reference · AR-5 · WF-102Core workflow
Change
Rescheduling inside WhatsApp
Customers can request a new time, review valid alternatives, and confirm the change without being sent to a separate rescheduling page.
Plan reference · WF-103Core workflow
Answer
FAQ assistance with guardrails
Answers come from approved business information. Low-confidence or materially ambiguous requests trigger clarification or human handoff.
Plan reference · AR-604Core workflow
Remember
Customer calendar handoff
After confirmation, customers can add the persisted appointment to Google Calendar, Apple Calendar, or Outlook for personal reminders.
Plan reference · WF-205Planned rollout
Connect
Channel-aware by design
Business-owned WhatsApp, Instagram, Facebook, and webchat endpoints are part of the planned architecture, subject to provider permissions and rollout validation.
Plan reference · AR-206Planned rollout
Follow up
Consent-aware lifecycle messages
Planned thank-you and rebooking messages recheck consent, booking state, recent contact, and suppression rules before sending.
Plan reference · WF-3 · WF-4Clear division of responsibility
Helpful language understanding. Deterministic business actions.
WAHNX keeps the flexible part of a conversation away from the controls that decide whether an operational action is valid.
AI can assist
Interpret and clarify
- Answer from approved FAQ information
- Identify a likely booking or rescheduling intent
- Extract candidate service, date, and time details
- Ask a focused question when the request is unclear
Workflows must decide
Validate and commit
- Resolve the correct business and authorized role
- Enforce availability, policies, and required fields
- Apply consent, idempotency, and version checks
- Persist a booking only after explicit confirmation
When confidence is low
WAHNX asks for clarification or routes to a person. It does not guess a transaction.
Who it is being designed for
Appointment-led local businesses.
The strongest fit is a business with clear services, availability, booking policies, and repeat questions customers ask before scheduling.
Personal care teams
A strong fit when service duration, staff availability, and rescheduling policies shape every appointment.
Salons, barbers, and grooming studiosWellness appointments
Useful where customers often ask the same preparation questions before choosing an available time.
Wellness studios and independent practitionersProfessional consultations
Designed for appointment requests that need a few structured details before a valid slot can be offered.
Advisors, consultants, and specialist servicesLocal service appointments
A practical fit when a business wants one controlled path from an inbound message to a confirmed visit.
Local service teams with scheduled visitsPilot readiness
Built for a careful pilot, not a rushed launch.
Public availability depends on provider approvals, operational checks, and evidence that booking behavior remains correct under duplicate, concurrent, failure, and timezone cases.
Build and validate the operating rules
Tenant boundaries, booking transitions, consent records, and failure handling are part of the launch gate—not afterthoughts.
Complete provider onboarding
Meta eligibility, channel permissions, template rules, and commercial assumptions must be verified before public availability.
Target controlled availability in 2027
The current plan targets February 2027, with March reserved as schedule buffer if approvals or launch checks remain open.
Pricing status
Final plans will follow commercial validation.
Included WhatsApp usage will be published only after Meta billing rules, regional rates, provider fees, and chargeable units have been verified.
Clear by design
Questions, answered without the fine print.
What WAHNX is planned to do, where the boundaries sit, and what still depends on provider approval.
AI is limited to interpreting customer intent, extracting details, asking for clarification, and answering from approved FAQ content. Structured workflows—not AI—enforce required fields, permissions, booking rules, availability, consent, and confirmation before an action can be committed.
That is the planned rescheduling experience. The workflow identifies the relevant booking, checks the business’s rules and current availability, offers valid alternatives, and requires the customer to confirm the change inside the conversation. It does not rely on an external rescheduling link.
WhatsApp, Instagram, Facebook, and web chat are in the product plan. Actual channel availability is subject to provider onboarding, permissions, policies, and the capabilities each provider makes available; support should not be assumed until those checks are complete.
No. The WAHNX booking record remains the source of truth. After a booking is confirmed, planned Google, Apple, and Outlook calendar handoffs can help a customer manage personal reminders, but they are secondary and changes there do not update the WAHNX booking.
Final pricing has not been published. Any working tiers are planning hypotheses until current Meta billing rules, regional rates, provider or platform fees, and observed usage are validated before launch.
It may be possible, but it is not automatic. Eligibility depends on Meta onboarding, the number’s current setup, account status, and applicable provider rules. The available path must be confirmed for each business during onboarding.