Know what happened. Know what needs you.

Evarmont records transport status and business outcome separately. A call can finish normally without producing a booking. Staff can review the result rather than infer success from the length or status of a conversation.

The call record, event timeline and callback queue offer different views of the same work. Recording and transcript availability are shown explicitly; a missing recording is not represented by an empty player.

The backend validates appointment rules and protects overlapping allocations at the database boundary. Repeated booking requests use an idempotency key. Rescheduling and cancellation keep the booking and its allocation in one transaction.

An assistant’s words do not confirm an appointment. The successful booking transaction does. If required checks fail, the system must not announce a booking that does not exist.

Durable side effects are recorded with the domain change and handled by workers after commit. Jobs use atomic claiming, bounded attempts and retry delays. Exhausted or permanent failures enter a dead-letter state with a reason for operators.

Calendar, CRM and team communication integrations are in development. Their delivery state is distinct from the underlying business outcome. A provider accepting a request does not prove that a person received it.

Integration settings show available operations, selected resources and connection states. Health checks are requested explicitly. Revoked access or a missing channel requires attention; a connection is not silently replaced with another provider.

Organization defaults and location choices are explicit. If several connections could perform an operation and no binding resolves the choice, the operation is refused instead of guessed.