--- title: 'Elora AI Assistant integration' summary: 'Connects your PBX to Elora and lets you manage your Elora AI assistants from inside the Cockpit.' section: features tags: - telephony - integrations - elora - ai updated: '2026-09-17' --- > The Elora AI Assistant integration links your PBX to your Elora account and opens the Elora dashboard inside the Cockpit, so you can manage your AI assistants without signing in separately. ## Overview Elora AI Assistant is one of the integration types you configure under [Integrations](integrations.md). Unlike most of the others, it asks for no credentials at all: the connection to Elora is made with a platform key held by MixVoIP, so all you provide is the email address that should own your Elora account. > [!NOTE] > This integration type is only visible if MixVoIP has enabled Elora for your platform and for your PBX. If you cannot find it in the **Type** dropdown, it has not been enabled for you — contact MixVoIP support. Only one Elora AI Assistant integration can exist per PBX. If you already have one, the create form points you to it instead of letting you add a second. ## What it does Saving the integration does four things: 1. Signs a request to Elora on your behalf using the platform key. 2. Creates your Elora account if you do not already have one, named after your PBX. 3. Records whether the connection worked, shown as a status badge on the form. 4. Creates the **SIP trunk** your Elora assistants speak over, once the integration is both connected and active. Once connected, a **Manage Elora Assistants** button appears. It opens the Elora dashboard full screen inside the Cockpit, so you can create and edit assistants, manage knowledge and see your agent dashboard in the same place you manage the rest of your telephony. ## Fields - **Elora admin account email** - the address that becomes the administrator of your Elora account. It is prefilled with your own Cockpit email address, and you can change it before saving. > [!WARNING] > Changing this address later does **not** rename the existing Elora administrator. It creates an **additional** Elora user under the same account. Set it to the address you actually want to own Elora before you save the first time. - **Elora AI Assistant active** - the single on/off switch for the integration. Turning it off hides Elora from this PBX and removes the dashboard button. Your Elora data is kept, and turning it back on restores access. ## Connection status A badge on the form reports the state of the connection: - **Connected to Elora** - the platform key was accepted and your Elora account is reachable. - **Connection failed** - Elora refused the request. A short explanation appears underneath. Because the credentials belong to the platform rather than to you, a failure here is almost always something only MixVoIP can fix, so the message will usually ask you to contact support. - **Not connected yet** - the integration has been created but not yet checked. - **Inactive** - shown alongside the connection state when the switch is off. The check runs when you first save, when you change the admin email, and when you activate the integration. It does not run on an unrelated edit, because contacting Elora also creates the account. ## Managing your assistants The **Manage Elora Assistants** button appears only while the integration is both connected and active. It opens the Elora dashboard in a full-screen window over the Cockpit, with a close button in the top-right corner. Each time you press the button a **new, single-use** Elora session is opened, valid for five minutes. Closing the window ends the embedded session. Reopening it starts a fresh one, so you may be asked to wait a moment while it loads. > [!NOTE] > Because the Elora dashboard is Elora's own application shown inside a frame, what you see in that window - and what you can do in it - is governed by Elora, not by your Cockpit permissions. Anyone who can edit this integration can open the dashboard with full access to your Elora account. ## Your SIP trunk Every Elora assistant on this PBX is reached over **one shared SIP trunk**, created for you as soon as the integration is connected and active. You never build it by hand, and there is nothing to fill in. Once it exists, a **SIP trunk** section appears on the integration form with everything Elora needs: - **Trunk name** - the name of the trunk on your [Parent SIP devices](parent_sip_devices.md) page. - **SIP username** and **SIP password** - the credentials Elora registers to your PBX with. The password is hidden until you reveal it, and can then be copied. - **PBX SIP host** - the address of your PBX that Elora registers against. - **Destination host** - where your PBX sends calls out to Elora. > [!WARNING] > The SIP password is a credential for your phone system. Only operators who can update integrations can reveal it, and every reveal is recorded. Turning the integration off disables the trunk but keeps it, credentials and all, so turning it back on restores service without anything having to be reconfigured on Elora's side. Deleting the integration removes the trunk. > [!NOTE] > If the section is replaced by a message saying no trunk has been created, your assistants cannot receive calls. Save the integration again; if the message stays, contact MixVoIP support. ## Wiring an assistant to your PBX Creating an assistant in Elora does not make it reachable by phone. The **Elora AI assistants** page in the Cockpit is where you give it a place on your PBX: 1. **Sync assistants with Elora** brings the current assistant list into the page. 2. Press **Create call flow** in the **Call flow** column. 3. Press **Send to Elora** in the **SIP sent to Elora** column. **Create call flow** builds one thing: a [call flow](call_flows.md) whose single step hands the call to that assistant over the shared trunk. It does not create a SIP carrier, and it does not take an extension. > [!IMPORTANT] > The new call flow is not attached to anything yet, so nothing reaches the assistant until you point something at it. Send a [phone number](phone_numbers.md) to it, add it as a step in another call flow, or use it as a queue overflow - whichever suits how you want callers to arrive. > [!IMPORTANT] > None of this reaches the phone system until you **push the configuration**. Until then the Cockpit shows the new setup but calls still follow the old routing. Pressing the button again on an assistant that already has a call flow is safe: it repairs the assistant's own step and leaves any step you added alongside it untouched, so a retry after a failure never leaves a second copy behind. ### Sending the trunk to Elora The two columns are the two halves of the same job. **Call flow** is your side - the route a caller travels. **SIP sent to Elora** is their side: Elora still has to know which trunk to register against. **Send to Elora** shows the assistant and exactly what Elora will receive: - the **SIP address** the agent registers against; - the trunk's **user name**; - the trunk's **password**. These are the same shared trunk credentials for every assistant on the PBX - sending them for one assistant sends the same values as sending them for another. What differs per assistant is which Elora agent they are recorded against. > [!WARNING] > This is the one action on the page that shares a password with Elora. It needs permission to update integrations, so an operator who cannot see that password cannot send it either. If Elora refuses the request, the column reads **Failed** and the message says why. Nothing on your PBX is changed by a failed send, so it is always safe to try again once the cause is fixed. ## See also - [Integrations](integrations.md) - the integration entity and its full field reference. - [AI features](ai_features.md) - the other AI capabilities available on the PBX.