Virtual Assistant · Integrated local candidate · Telephone acceptance pending

Overview

Virtual Assistant · Independent SIP receptionist
Disconnected
Sign in with your Virtual Assistant account. The local administrator token remains available during migration.
Administrator migration access
Sign in with your account, or use the existing administrator token during migration.
CRM contacts
—
Saved customer records
Booked appointments
—
Current active reservations
WhatsApp queue
—
Pending · not sent
Telephone process
Unknown
SIP registration not verified

Upcoming appointments

Connect to load appointment records.

Operational overview

Telephone voice service

Service status will appear after connecting.

Appointment & CRM integration

Local business database; live voice linkage requires acceptance.

Meta WhatsApp

Queue storage only. Delivery not enabled or verified.

Appointment calendar

Database-backed

Book an appointment

Times are converted to UTC before saving. Double bookings are rejected by the server.

Calendar information

Appointment records are saved in the same business database used by the telephone integration.

This is a working appointment list, not yet a drag-and-drop calendar or Google/Microsoft Calendar sync.

Visual appointment calendar

Month
Dates are displayed in your browser's time zone. Canceled reservations are shown in gray.

Appointments

Connect to load appointments.

Add or update CRM contact

Open an existing record to edit it. Customer IDs remain stable when the phone changes.

Customer records

Use CRM contacts for appointment booking and future customer messaging.

Call history and caller identification are not yet connected to this screen.

All contacts

Connect to load contacts.

Queue a WhatsApp template

Queue only. This does not send any WhatsApp message. Meta integration is not yet enabled.

Meta Cloud API

Not connected

Actual transmission, delivery status and webhook processing still require a verified WhatsApp Business integration.

Queued messages

Connect to load queue.

Sofía telephone service

Not checked

Connect to check the process.

Checks the Debian systemd process only. This does not confirm SIP registration or call audio.

Configured architecture

Grandstream GCC6011 → PJSUA2 / RTP → OpenAI Realtime

Current tested destination: extension 1300.

Call controls

Call transfer and hangup remain managed by the separate voice service.

No buttons on this page modify live SIP registration or calls.

Easy Setup

Draft configuration
Settings are saved as drafts. SIP TLS requires a certificate, PBX support and a separate activation test; it does not change the live voice service.

AI Center — Provider configuration

OpenAI Realtime is the existing voice integration; this local panel does not verify live calls. Preference is saved but does not change phone calls until an adapter passes integration tests.

Checking...

Provider integrations

Credentials and live routing require separately tested adapters. This page does not accept API keys.

Operations & integrations

Sofía Voice

Live service process status is checked on Telephone Status. SIP registration and active calls are not yet monitored here.

Appointments + CRM

Live shared SQLite records from telephone tools and this panel. Appointment validation remains enforced server-side.

WhatsApp Business

Messages are queued locally. Meta delivery, approved templates, webhook verification and delivery receipts require activation.

AI Center

OpenAI Realtime is the tested provider. Gemini and Ollama require adapter implementations before becoming selectable.

SIP Security

TLS is a draft option only. Certificates and PJSUA2 TLS registration must be tested before activation.

Maintenance

Backup and rollback of panel code exist; production database backup scheduling and unified updates remain pending.

Live Integrations & Diagnostics

OpenAI remains the live telephone voice. Other providers are optional until their voice adapters are verified. WhatsApp messages are sent only when you explicitly confirm.

Sign in to view readiness.

Send an approved WhatsApp template (Meta)

This sends a real message using Meta Cloud API if configured. Meta acceptance does not guarantee delivery. The recipient must have the required consent.

API tokens and PBX passwords are not collected here. Configure /etc/amevoip/meta.env on the server. SIP TLS and other providers' live call routing are not activated by these controls.

System & safety

This portal operates on a protected local API and is intended for LAN/VPN access.

ComponentCurrent scope
CRM / appointmentsReal local SQLite data
Telephone statusRead-only systemd process check
WhatsAppQueue only — no Meta delivery
Easy SetupDraft settings including TLS — not applied
Telephony voice programUnmodified by this dashboard update
Multi-tenant & installerNot production-validated

Modern Enterprise interface update. Does not certify the complete commercial product.

CRM Activity Notes

Internal notes saved in the same database as contacts and appointments.

Scheduled Tasks

View existing queued jobs. No automatic sending is implied.

Settings

Local administration · Settings do not apply to live PBX

General & PBX (non-secret)

These settings are stored locally. SIP credentials and API keys are not entered here.

Provider & local API diagnostics

API credentials are kept outside this page. No tokens or passwords are displayed.

Users & roles

Manage individual accounts in Users & Roles. Retire shared token access only after testing an owner account.

Users & Roles

Account migration

First sign in with an owner username and password, then retire shared token access. Your account remains active.

PBX & Operations

Reschedule appointment