A booking should close as completed or no-show before follow-up becomes meaningful.
Follow-up
Post-session follow-up
Follow-up is the part of the consulting lifecycle after the video call: mark the outcome, give the client a useful next step, preserve the confirmation pass as the access record, and keep live provider delivery honest until WOP/SMTP smoke proof exists.
Clients can keep optional reminder and follow-up channels separate from transactional booking messages.
Next steps should route through Consulta surfaces: confirmation pass, account recovery, rebooking, retainer review, or contact.
Completed and no-show outcomes
Consulta should not leave past sessions in an ambiguous active state. The operator can treat a past booking as completed or no-show before deciding whether any client follow-up makes sense.
- Completed means the session happened and the client may need a recap, rebooking path, or reviewed next step.
- No-show means attendance failed; refund, policy, and rebooking decisions remain separate from the status label.
- Outcome state should never expose Beam host links, payment provider refs, or private client contact values publicly.
Optional client follow-up
Post-session follow-up can share a short recap, next action, rebooking link, retainer review path, or support route. It should not become a generic marketing blast or bypass client channel preferences.
- Transactional booking messages still carry confirmation, reschedule, cancellation, and access-pass recovery.
- Follow-ups are optional lifecycle messages and can be disabled separately from required booking-state messages.
- The confirmation pass remains the durable place for booking details, calendar actions, policy state, and recovery.
Client next-step paths
A useful handoff should match the session outcome. Some clients need another paid session, some need a reviewed retainer, some need a workshop or service package, and some only need the agreed notes or next decision.
- Use rebooking for another focused session when the next problem is clear.
- Use retainer review when recurring advisory or operations support is real.
- Use Contact when the next step needs a custom implementation quote or provider setup discussion.
Consultant handoff and provider gates
For consultants, follow-up should make the operating state visible: what happened, whether the client can receive optional messages, what was sent or simulated, and which provider gates remain open.
- Logging mode is useful for demos and local smoke tests, but it is not live email or WhatsApp delivery.
- Live WOP/SMTP delivery requires credentials, approved senders/templates where applicable, callback behavior, and evidence.
- Follow-up content should not include raw Beam links, payment refs, dashboard links, or provider internals.
What is not live yet
Follow-up is also a product boundary. It can support retention, rebooking, reviewed retainers, service packages, and later CRM notes, but it should not claim full workflow-builder, CRM sync, or automated sales operations before those rails are built and verified.
- No live CRM sync is claimed from this public page.
- No review-collection or survey automation is claimed live yet.
- No emergency, regulated-care, or unlimited-support follow-up is assumed.