Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.elementum.io/llms.txt

Use this file to discover all available pages before exploring further.

We’re always trying to improve our platform for our customers. Here, you can get an inside look at what’s currently in beta at Elementum. Remember, this list is provided as a heads-up—not as an invitation to test or a promise of what capabilities may be included. Most customers will not see these features until general availability. For what’s available today, see the most recent release notes.

​
What to expect

Heads-up, not a commitment. The information below explains how we treat beta features and why delivery and availability can change.
  • Currently being tested. These features are in active development and testing. Behavior and scope may change.
  • No guaranteed delivery date. We do not commit to a specific release date for any feature listed here.
  • No guarantee of delivery. Priorities shift based on resources and customer needs. A feature in beta may be delayed, changed, or not released to General Availability.
  • Limited availability. Some features may be tested by select customers before being released to General Availability. Broader access is not guaranteed until a feature is generally available.

​
Features in beta

This list is updated on a biweekly cadence to give you an idea of upcoming improvements likely to occur in Elementum. The colored badges indicate the area of Elementum where you will see the update.
​
Agent Email Conversation Action

​
Agent Email Conversation Action Intelligence

Kick off an agent-led email conversation from any automation to collect data, deliver information, or follow up with recipients—without blocking the workflow. Configure the agent, first message, additional instructions, and a 1–4 day conversation timeout, with dynamic record values supported for the message and instructions.
​
Studio Agents: Flow Builder

​
Studio Agents: Flow Builder Intelligence

A new coding-based agent type that builds automations, agents, and flows in Elementum through conversation. Describe what you need, and the Studio Agent generates the flow—lowering the barrier to creating complex workflows on the platform.
Who can configure it: App Administrators.Where to find it: App → Flows.Configuration steps:
  1. Open the Flows page and use the natural language chat at the top to describe the workflow you want to build. Explain the stages and automations you’d like included.
  2. Click the Send icon to hand the request off to the Studio Agent.
  3. Follow along in the chat pop-up as the agent writes the TypeScript that builds the flow. Click any action to see more details about what the agent did.
  4. Use the Preview pane to verify the workflow is being built as expected.
  5. If something doesn’t look right, keep chatting with the agent to refine the flow.
  6. Click Publish when the flow is ready. After publishing, you can manually edit each step of the flow.
Behavior notes:
  • In-progress builds appear under Studio Agent Sessions on the Flows page so you can resume a draft session later.
  • Pre-built prompt templates (for example, Expense approval, Customer onboarding, Incident triage) are available below the chat as starting points.
​
Accept Files Through Run Agent Task

​
Accept Files Through Run Agent Task Intelligence

The Run Agent Task automation action can now pass files directly to an agent for processing. Use it in place of the AI File Reader to get broader model support and expanded file-handling functionality. Learn more about Run Agent Task.
​
Cross-App Skill Sharing

​
Cross-App Skill Sharing Intelligence

When configuring skills on an agent, select Custom access to pull in active skills from any App in your organization—not just the agent’s own. Agents discover and use cross-app skills the same way they use local ones, and deployed agents automatically include the Apps that provide their configured skills. Build a skill once and reuse it everywhere—agents can tap into capabilities across your entire org without duplicating configuration. Learn more about agent skills.
Who can configure it: App Administrators.Where to find it: App → Agents → Configure → Skill Access.Configuration steps:
  1. Open the agent and click Configure.
  2. Expand the Skill Access section.
  3. Under Access Mode, click the settings icon next to Custom to edit the Custom skills available list.
  4. Search for and select the desired skill from another agent.
  5. Click Done.
  6. Click Save.
​
Voice Agent Gateway

​
Voice Agent Gateway Org Settings

Assign a single phone service to an Agent Gateway so one phone number becomes the entry point for multiple voice agents. Inbound calls flow through a pre-agent pipeline that authenticates the caller, detects language, and classifies intent to route to the right voice agent. Configure voice overrides on each agent to give them a distinct persona. When a caller’s intent shifts mid-call, the gateway detects it and transfers them to a different agent—no re-authentication required, with full transcript context carried over. The same multi-agent orchestration available in chat is now available on the phone. Learn more about Agent Gateways.
Who can configure it: Organization Administrators.Where to find it: Settings icon Org Settings → Agent Gateways (under Platform).Prerequisites:
  • An Agent Gateway with at least one agent added and routing rules defined.
  • A configured phone provider (for example, Elementum Twilio or a SIP trunk-enabled provider).
Configure the gateway:Follow the steps in Agent Gateways to create the gateway, add agents on the Agents tab, and define how requests are routed on the Rules tab. The Settings tab now includes a Voice section for connecting one or more phone numbers to the gateway.Connect a phone number:
  1. Open the gateway and select the Settings tab.
  2. In the Voice section, click + Add phone number.
  3. In the Create Phone Service dialog, configure:
    • Number Type — Select how the number is provisioned (for example, Create Number).
    • Area Code — Enter a U.S. toll-free area code (for example, 833, 866, 877, or 888).
    • Phone Provider — Select the telephony provider that will host the number (for example, Elementum Twilio).
    • Caller Access — Choose who can reach the gateway (for example, Allow All Callers).
    • Default Language — Set the primary language used for caller interactions.
    • Additional Supported Languages — Optionally add languages the gateway can detect and respond in mid-call.
    • Generate First Message — Toggle on to have the gateway automatically generate the opening message when a call connects.
  4. Click Save.
Connected phone numbers are listed under the Voice section. Add more than one phone number to give the gateway multiple inbound entry points.Behavior notes:
  • Inbound calls are authenticated, language-detected, and intent-classified by the gateway before being routed to the right voice agent based on the gateway’s rules.
  • When a caller’s intent shifts mid-call, the gateway transfers them to a different agent without re-authentication and carries the full transcript across the handoff.
  • Configure voice overrides on each individual agent to give them a distinct persona on calls routed through the gateway.
​
SIP Trunking Provider

​
SIP Trunking Provider Org Settings

Bring your own telephony provider to Elementum by connecting SIP trunk-enabled phone providers to power voice agents.
Who can configure it: Organization Administrators.Where to find it: Organization Settings → Integrations → Phone.Prerequisites:
  • A SIP trunk-enabled account with a supported provider (for example, Twilio, Telnyx, or any standards-compliant SIP provider).
  • Credentials and the SIP URI/domain from your provider.
Configuration steps:
  1. Add a new phone provider and select SIP Trunk as the connection type.
  2. Enter a Name, add one or more SIP Gateways (the IP addresses or hostnames that will handle call routing), and select an Authentication Type.
    • IP Based — authenticate using the gateway’s IP address; no additional credentials required.
    • Credentials — enter a username and password.
  3. Use the provided callback URL to complete the provider configuration.
  4. Test the connection to confirm Elementum can register with the trunk.
  5. Assign inbound/outbound phone numbers from your provider to specific voice agents.
Behavior notes:
  • Using your own SIP trunk lets you keep existing carrier contracts and phone numbers while routing calls through Elementum’s voice agent stack.
  • Per-call audio, transcripts, and telemetry still flow through Elementum for logging and agent memory.
  • Outbound caller ID and number porting are handled by your telephony provider, not by Elementum.