MADPBX homeBeta status · English

Private beta · Updated 19 October 2026

See what is ready.
Know what comes next.

The MADPBX Control Room is an owner-restricted development beta. It is not a publicly available telephone service or a production PBX replacement.

VERIFIED IN PRIVATE BETA

Reception practice

Four saved routing scenarios matched their expected outcomes: staff available, nobody available, business closed and transfer failure. These are simulations; they place no telephone calls.

CONNECTIVITY CHECK PASSED

Local AIdea gateway

The Control Room reached the configured local gateway and confirmed a model was installed. This does not prove answer generation, speech or end-to-end calling.

IN DEVELOPMENT

Connected communications

Real TrAIt calls, the Averon helpdesk journey, speech services and callback delivery still require integration and testing. No readiness date is promised here.

NEW · SETUP PRESETS

Choose a business, organization or place

17 starting points cover hospitals, schools, dentists, businesses, religious and public places, homes and buildings. Search, preview, apply or undo suggestions, edit your greeting, then save a separate reception draft. Existing routes are not activated or replaced.

First implementation: suggested department, enquiry topics, knowledge checklist and greeting. External bookings, messages, website learning and physical-access integrations are not connected by selecting a preset.

Who can open the beta?

The current Control Room is restricted to its owner. The link below does not grant access or enroll you as a tester. Prospective pilot partners can email an enquiry; access is not automatic.

Opens your email application. Nothing is submitted on this page.

Development roadmap

Compatible equipment, private connections

Planned: an on-site connector that initiates authenticated outbound connections, limits access to approved services and checks compatibility. Hardware remains subject to firmware, network and security requirements; not every device will be supported.

Language belongs to the caller

Planned: preferred-language routing, suitable human agents and disclosed AIdea interpretation for tested language pairs. Unsupported languages must have an honest fallback. Broad language packs follow product testing.

One MAD ecosystem

TrAIt is the intended communication client, AIdea the intelligence layer, and Averon the first integrated helpdesk pilot. These connections must pass complete user-journey tests before being described as available.