Catch the customer before the hype disappears.
Three booking paths, one source of truth. This demo separates work that can safely move straight to a deposit from work needing fast review or a real consultation.
Try the three routes ↓Not every tattoo needs the same amount of friction.
RMT's current journey treats a simple walk-in-size request and a large cover-up almost the same. The target system uses hard routing rules before preference: fixed-scope work can move fast; clear custom work gets one asynchronous review; complex work keeps the consultation.
Try the three customer paths.
Improve the joins before replacing platforms.
The recommended first implementation is a low-change hybrid: Wix explains and routes; Jotform collects detailed briefs only where needed; Square remains calendar, appointment and payment truth; a small Cloudflare coordinator preserves source and state.
| Path | Solves | Trade-off | Use now? |
|---|---|---|---|
| Low-change hybrid | Lower latency without replacing Square or the Jotform archive. | Requires clean IDs/webhooks and staff state discipline. | Recommended pilot |
| Wix-native consolidation | Fewer customer handoffs and native website analytics. | High migration/reconciliation risk while Square remains operational truth. | Only after sandbox proof |
| Custom coordinator | Best routing, holds, attribution and automation. | More build and maintenance cost. | Earn after pilot |
Measure deposited, booked capacity—not clicks.
qualified inquiry → deposit paid, by route, source, location and artist
median minutes from first landing to deposit or confirmed next step
booked tattoo hours, completed revenue and otherwise-idle hours filled
staff minutes and messages required per deposit-paid booking
artist override, misroute, cancellation, no-show, refund and complaint rates
percentage of inquiries that reconcile to a Square appointment and deposit
Two small decisions, then a measured pilot.
Approve or change the three-route shape.
Are direct deposit, fast review and mandatory consultation the right visible choices? If not, name the route or wording that feels wrong.
Define the business rules that make each route real.
Which services may take a Square deposit directly, what confirms a booking, how long a hold lasts, and which response-time promise staff can sustain.
What this draft is grounded in.
- Live RMT/Wix mobile and traffic reads, Google Search Console, Square aggregate results, current Jotform route inspection, and relevant staff email threads.
- Square Bookings API and Square appointment deposits.
- Jotform conditional logic, prefilled fields, and webhooks.
- Google cross-domain measurement guidance.