WhatsApp and inbox
Live demo-safe today
Public-facing demos can already show governed conversation handling, lead capture, and human follow-up paths.
Voice
Selected-plan guided demos
Voice remains available for guided demonstrations and selected packages rather than being marketed as a default for everyone.
Bookings
Operational scheduling path
Appointments, team calendars, and booking handling can be shown as part of the wider operational workflow.
Billing
Public package baseline
Packages, usage visibility, and payment-flow direction already exist in the broader platform baseline.
Business problem
Why businesses pay for this instead of handling everything manually
Messages arrive through WhatsApp, phone, forms, or social channels, but the handling after that is often inconsistent and difficult to track.
High-intent enquiries are easy to miss when one person is trying to remember replies, follow-up, bookings, and next actions by hand.
Businesses end up repeating the same answers, losing visibility, and relying too heavily on whoever happens to be behind the desk that day.
Owners need clearer control over what was asked, what happened next, who needs to respond, and what still needs attention.
Operational workflow
What the platform is designed to do
Step 1
Capture the enquiry properly
Bring customer contact into one governed flow instead of leaving it spread across messages, calls, and memory.
Step 2
Extract useful operational detail
Turn inbound conversations into lead details, follow-up context, booking intent, and owner-visible actions.
Step 3
Support human handling where needed
Route handoff, callbacks, bookings, and review steps cleanly when a person needs to step in.
Step 4
Give the business more control
Keep visibility, notifications, audit-safe history, and usage-aware billing in one operational workspace.
Capabilities
Demo-ready capability areas
The platform is presented as a governed operational system. These are the public-facing areas that are safest to explain and demonstrate today.
Governed inbox handling
Help businesses centralise WhatsApp enquiries, keep replies consistent, and reduce missed follow-up.
Voice support for selected plans
Demonstrate voice-first handling, human transfer, and controlled call workflows where the package and setup allow it.
Lead capture and follow-up visibility
Capture useful lead details, link follow-up, and keep owner visibility stronger across new enquiries and handoffs.
Appointments and guided scheduling
Support appointment intent, booking flows, team calendars, and follow-up around booked work.
Notifications, ownership, and review
Route the right alert to the right person and keep operational ownership clearer for the business.
Billing and usage visibility
Show what is included, track usage cleanly, and keep payment and access handling inside a proper SaaS flow.
Fit
Where it fits best
High-message service businesses
Useful for teams that receive regular enquiries and need better handling, faster follow-up, and fewer dropped conversations.
Appointment-led businesses
A strong fit where bookings, consultations, callbacks, and owner visibility matter alongside messaging.
Growing teams that want more control
Suitable for businesses that are moving beyond informal handling and need a more governed operational system.
Included direction
What we are comfortable showing publicly today
WhatsApp handling and inbox flow
Lead capture and follow-up visibility
Appointments and booking support
Human handoff, notifications, and owner review
Owner control, usage visibility, and billing readiness
Trust points
Reliability, security, and support still matter
Guided rollout
The current public route is guided demo, guided pilot, and assisted setup rather than promising instant self-serve onboarding before it is genuinely ready.
Security-aware product direction
The wider platform direction already includes encryption, audit, privilege-aware review, and owner visibility as product features rather than afterthoughts.
Shaped around the business
The platform is designed to be configured around real workflow, follow-up expectations, booking logic, and the way the organisation already operates.
Development team support
CAJ presents this as a development team and operational software partner, not a generic AI widget placed on top of a fragile process.
Screenshot showcase
Platform views to capture and prove during guided demos
This section is prepared for real platform screenshots after each feature path is tested. Until the final captures are added, the cards below act as proof-oriented placeholders so the sales path stays honest and ready for the finishing pass.
WhatsApp and inbox
Inbox workspace and conversation handling
Use this slot for the active inbox workspace once the final demo-safe screenshot is captured.
Ready for screenshot after guided test
Show a real inbound enquiry landing in the workspace.
Confirm the conversation history, lead context, and next action are visible together.
Prove that a human handoff or reply path is obvious from the same screen.
Appointments
Booking and scheduling flow
Reserve this slot for the appointments or calendar view used in the guided demo once the capture is approved.
Ready for screenshot after booking test
Show the booking path from enquiry to scheduled outcome.
Confirm that staff, time, or service context is visible clearly.
Use a capture that proves the platform helps with the work behind the booking, not only the booking itself.
Control and follow-up
Human handoff, notifications, and owner visibility
Use this slot for a screenshot that shows how the platform surfaces action, routing, or owner-level oversight after customer contact arrives.
Ready for screenshot after follow-up test
Show who needs to act next and why.
Prove that follow-up or notifications are linked to a real workspace.
Keep the capture on a guided demo-safe surface rather than a cluttered admin-only internal screen.
Commercial readiness
Package, usage, or billing confirmation path
Reserve this slot for the payment, billing, or package-proof view that supports the public commercial message once the test pass is complete.
Ready for screenshot after billing test
Use a capture that supports the package story shown on the public pricing page.
Confirm the screenshot looks presentation-ready and does not expose internal-only data.
Only use a flow that is already strong enough for a guided public demo.
Capture order
Suggested capture order for the final screenshot pass
When the final screenshot assets are prepared, capture them in the same order a serious prospect would understand the product: from the incoming enquiry, to the work created behind it, to the owner visibility and commercial proof.
Pass 1
Enquiry to visible action
Start with a realistic inbound message, then prove the platform turns it into a clearer operational record rather than just another chat window.
Capture the conversation arriving in the inbox.
Capture the lead, follow-up, or next-action context beside it.
Keep the final screenshot free of test clutter or unfinished internal labels.
Pass 2
Booking or service follow-through
Use a second proof path that shows the platform supporting a real business outcome such as a booking, callback, or guided staff action.
Show the booking or scheduling screen once the path has been tested end to end.
Use a capture that proves the platform supports the workflow behind the customer request.
Make sure the screenshot still matches the public package promise and the guided-demo story.
Pass 3
Owner trust and commercial reassurance
Finish with a view that supports why a business would pay for the platform: visibility, control, support, billing readiness, or another owner-facing proof point.
Choose a view that looks strong on both desktop and mobile crop ratios.
Keep sensitive or super-user-only information out of the final public asset.
Pair the screenshot with a short caption explaining the operational value, not only the screen name.
Guided onboarding
Current onboarding position
We currently offer guided setup for selected demo and pilot customers. This keeps the rollout honest while broader provider self-service approval is still catching up.
Book a guided demo to review the workflow, package fit, and what should be shown first.
Apply for early pilot onboarding if you want a more hands-on rollout path with assisted setup.
Expect guided configuration around channels, business hours, follow-up, and booking handling rather than an instant self-serve connection path for every tenant today.
Support and rollout
A calm public route matters as much as the features.
The website should explain reliability, support, onboarding, and honest scope clearly enough that a business owner understands what happens next before ever seeing a screenshot or a sales call.
Guided review
We review the workflow before promising a rollout.
The first step is to understand the enquiry path, follow-up pressure, booking needs, and package fit rather than pushing a generic sales script.
Assisted setup
Setup is currently guided for a reason.
While broader provider self-service approval is still catching up, the public route stays assisted so channels, hours, handoff, and customer expectations are configured properly.
Support
You are not left alone after the first call.
The public route includes guided onboarding, launch review, and a support model that matches the package and the business workflow being rolled out.
Honest scope
Only demo-safe features are presented publicly.
The website keeps the message on the parts of the platform that are already credible for guided demos and early pilots, without overstating unfinished modules.
Next step
Need to see the platform against your workflow?
Start with a guided demo rather than a vague sales call.
Book a guided demoPackages
Want to compare the public package options first?
Review the current pricing direction, onboarding position, support model, and where voice is intentionally limited.
View packagesPilot route
Need to talk about an early pilot or assisted rollout?
Use the pilot path when you already know the business need is real and want to discuss a more hands-on setup route.
Discuss an early pilot