Every serious question.
One clear answer surface.

Elarvio is a WhatsApp communication and appointment operations platform for service businesses. It connects customer conversations to approved company knowledge, live availability, bookings, and a shared team inbox.

No. Conversation is the entry point. The platform also models services, staff, locations, hours, booking rules, calendars, handovers, company content, billing, and operational audit events.

It can handle approved routine questions, collect structured intake, find valid appointment slots, confirm bookings, prepare reminders, and keep the full context ready when a teammate takes over.

It is designed to remove repetitive coordination and protect staff focus. Exceptions, sensitive questions, ambiguous requests, and controlled workflows remain visible and transferable to a person.

You enter onboarding, complete the company profile, connect WhatsApp, add services, staff, locations, hours and knowledge, test an inbound message, and then activate the workflows you approve.

No. Registration and setup are self-service. The interactive product experience is public, and your workspace contains the real activation path.

Have access to the Meta Business account, the WhatsApp number, service durations and prices, staff schedules, opening hours, booking policies, and the customer questions your team answers repeatedly.

Yes. The Company workspace lets authorized users update the logo, brand colours, public text, contact details, booking introduction, FAQs, policies, and public visibility.

Inside Integrations, start Meta Embedded Signup, authorize the Business account, select the WhatsApp Business Account and phone number, then complete the webhook and inbound-message health check.

Eligibility depends on the number's current WhatsApp and Meta configuration. The connection flow exposes the available numbers; migration constraints must be checked against the current Meta account state.

Integration credentials stay server-side and are encrypted before database storage. They are not returned to the browser or embedded in public code.

An authorized teammate can take over a conversation. The customer history and operational context remain together so the teammate does not restart from zero.

The slot engine combines location hours, staff working time, absences, service duration, before-and-after buffers, minimum notice, booking horizon, existing appointments, and temporary holds.

No. The intended booking path only offers slots returned by the availability engine. The server checks the selected slot again when the customer confirms.

Yes. Each published company can expose a mobile-ready booking page using the same services, staff, policies, public content, and availability rules.

The operation should surface the sync state rather than silently claim success. Teams can see pending or failed synchronization and resolve the exception.

Starter suits a focused single-location operation. Professional adds capacity, automation and reporting for a growing team. Business supports larger multi-location operations. Enterprise is scoped for custom governance and deployment needs.

After registration and sign-in, an authorized billing owner chooses a plan and cadence. The server creates a Stripe Checkout Session; card details are entered on Stripe's hosted surface, not on Elarvio pages.

When Stripe is configured, billing owners can open the Stripe customer portal from the dashboard for supported payment-method, invoice, and subscription actions.

The configured annual price includes two months compared with paying the listed monthly price for twelve months. Applicable taxes and approved provider or overage costs remain separate.

Server-side membership and permission checks scope protected reads and writes to an organization. A company identifier sent by a browser is never sufficient authorization by itself.

Sensitive public mutations use bounded payloads, same-origin checks, rate limits, honeypots where appropriate, and a short-lived signed proof-of-work challenge bound to the requesting client and accepted only once.

No responsible team can promise that. The platform uses defense in depth and should still receive continuous patching, monitoring, dependency review, external testing, incident response preparation, and production infrastructure hardening.

It explicitly instructs visitors not to share passwords, access tokens, card data, or sensitive customer information. Public chat history is limited and should be treated as a product-information channel.