AWS development status
Existing AWS connection
Sign-in uses the existing Cognito account and multi-factor authentication. Administration and customer screens request authorized AWS data; there is no mock-data fallback.
Customer, location and receptionist configuration workflows use revision-checked saves. Published configurations remain separate from drafts and do not activate live calls.
Deployment checkpoints
New dashboard, membership, invitation acceptance, corporate-default and handoff capabilities require the AWS update. Their controls remain unavailable until the service advertises support.
Invitations can produce private acceptance codes after deployment; email delivery and new Cognito account provisioning are not configured. A code is not active access until accepted by the invited verified account.
Local automated tests do not prove deployment or your real signed-in session. Sign-in, refresh, sign-out and cross-customer checks must be repeated against AWS after deployment.
Unavailable
Live calls, phone provisioning, voice gateway, SMS, booking, payments, billing, usage, analytics, calendar/CRM and Broadvoice account integration are not enabled.
Ownership reassignment and multiple customer memberships per identity are not implemented. Existing IDs and administrator memberships are preserved.