ERA AI Agent — One Intelligent Workspace for Customer Engagement & Automation
Voice WhatsApp email supported social engagement business knowledge bookings reporting and workflow controls — brought together in one intelligent platform
Turn customer requests into clear next steps
Start with a real customer interaction ERA can understand the request follow the configured workflow and help carry out the next step while keeping the team informed
Explore the ERA workspace before the demo
This sample interface illustrates major product areas and does not display live customer or production data
From answer to action in one connected flow
An agent connected to business systems should understand the request and its context carry out the appropriate action and record the outcome clearly for the team
One ERA Multiple channels
Keep one consistent operating layer across the channels your business enables
Six Core Capabilities One Connected Platform
Bring customer interactions business knowledge workflows and operational controls together in one connected platform
AI Voice & Telephony
Create inbound and outbound AI voice agents manage numbers SIP trunks and routing and monitor call quality and availability
Discuss This CapabilityKnowledge Base
Structure approved business knowledge so agents can answer using current relevant information across supported content types
Discuss This CapabilityWhatsApp Bookings & Calendar
Use templates and two-way workflows automate reminders and confirmations and manage appointments meetings and calendar visibility
Discuss This CapabilityInstagram Automation & Engagement
Automate supported DMs comments comment-to-DM actions mentions triggers and follow-ups based on available Meta permissions
Discuss This CapabilityReports Billing & Performance
Track usage and performance review activity manage subscriptions and maintain visibility into channel usage
Discuss This CapabilityControls Notifications & Administration
Manage alerts workflow controls users teams roles and centralized administration within one operational layer
Discuss This CapabilityDesigned for controlled business use
Manage users teams and operational permissions
Ground agents in approved business information
Connect workflows and systems through defined integration points and permissions
Keep usage alerts and operational activity visible
Choose capacity around the way you work
Compare available capacity then discuss the channels and workflows you want to run The figures below come from the listed plans
Starter
SAR 699/ monthA starting point for a focused workflow Choose a clear agent task prepare the relevant knowledge and observe usage before expanding
- Usage credits
- 7,000 credits
- Agent capacity
- Up to 2 agents
Published details for this plan
Easy entry to automation
What can these credits cover?
WhatsApp/Instagram: 7,000 messages Voice: 700 minutes SMS: 1,750 messages
Each estimate allocates the entire credit balance to one channel When you combine channels they draw from the same balance; these capacities are not added together
We define channels integrations support and setup scope in the agreed proposal around your requirements and operating model
Discuss this planWhatsApp email and Instagram: 1 credit/message SMS: 4 credits/message Voice: 10 credits/minute
Provider fees: third-party WhatsApp and SMS fees are separate unless otherwise agreed
Compare capacity and pricing
| Plan | Price | Usage credits | Agent capacity |
|---|---|---|---|
| Starter | SAR 699 / month | 7,000 credits | Up to 2 agents |
| Growth | SAR 1,399 / month | 14,000 credits | Up to 5 agents |
| Professional | SAR 2,999 / month | 28,000 credits | Up to 10 agents |
| Professional Plus | SAR 3,999 / month | 40,000 credits | Up to 15 agents |
| Enterprise | From SAR 5,999+ / month | 56,000+ credits | Custom |
What is an agent?
An agent is an AI assistant configured with knowledge instructions and a workflow The listed count describes agent capacity not employee seats or simultaneous calls
What do credits mean?
Credits measure usage not the number of customers Consumption varies by channel and interaction type; see the usage details and provider fees below the plans
Are all channels and features included?
This page describes ERA’s overall capabilities Your subscription scope is agreed around the channels integrations knowledge and workflows you need including any associated third-party fees
How do I choose capacity?
Start with the agents you need expected interaction volume and channels Include these in your demo request so the capacity and implementation scope can be assessed
Common questions before a demo
01Do I need technical experience to use ERA?
ERA provides a workspace for managing agents and interactions The technical expertise needed for setup depends on the channel integrations and workflow you want to enable
02Does ERA support Arabic?
ERA is designed for business interactions in Arabic and other languages Language and dialect performance should be validated for each intended use case before deployment
03Can ERA connect to my current systems?
ERA supports workflows that connect business systems The exact CRM ERP API or internal-system connection depends on the target system and approved integration scope
04Can ERA work across several channels?
Yes ERA is designed around voice WhatsApp email and supported social engagement with additional channel capabilities enabled according to the required setup and provider permissions
05What happens when the agent does not know the answer?
The recommended setup is to keep responses grounded in approved knowledge and define fallback or escalation behavior instead of allowing unsupported answers
06How are credits calculated?
Current packages calculate credits based on channel usage Voice messaging and provider-related costs can differ and external provider fees may be separate
From conversation to the systems where work actually happens
ERA is most useful when customer conversations do not stop at an answer Connect supported systems approved data sources APIs and workflows so the next configured action can move forward with the right context
Connect the tools your teams already use
Integrate supported CRM booking service business applications and internal systems through configured APIs and integration services
Move context between the conversation and your workflow
Use supported APIs and webhooks to retrieve approved context pass structured information and trigger configured downstream steps
Ground responses in the information you approve
Give the agent access to configured business knowledge so common questions and workflows can use more consistent organizational context
AI automation needs control not just intelligence
ERA is designed around configurable access approved knowledge controlled integrations and workflow boundaries so organizations can define how the agent should operate within each use case
Explore Security & Trust →Questions teams usually ask before starting
Start with one clear use case validate the workflow then expand channels knowledge and integrations based on what the business actually needs
Does ERA only answer customer questions?
No ERA can be configured around conversations and business workflows Depending on the implementation a flow can use approved knowledge capture structured information connect to supported systems and help move a configured next action forward
Which channels can ERA support?
The current product experience highlights voice WhatsApp email and supported social channels The exact channels available for a deployment depend on the configured integrations and account setup
Can ERA connect to our existing systems?
Integrations can be designed around supported APIs webhooks and integration services The actual connection depends on the target system available interfaces authentication data requirements and the workflow being implemented
Do we need to automate everything from day one?
No A practical rollout can begin with one measurable use case and a controlled workflow then expand once the experience knowledge and integrations have been validated
Can the agent use our company knowledge?
ERA can be configured to use approved organizational knowledge relevant to the use case The knowledge scope and operating instructions should be defined as part of the implementation
How do we know whether ERA fits our use case?
Start with the business outcome: what interaction happens today what information is needed what system is involved and what action should happen next A demo can then be shaped around that real workflow
Bring us one workflow We will show you where ERA can fit
Tell us the channel the customer interaction the systems involved and the outcome you want We can use that context to shape a more relevant demo
Ready to see ERA in action?
Tell us the workflow or customer journey you want to improve and we will show you how ERA can fit


