From SLA cases to reseller portals: Agentforce agents for telecom firms

20 October 2026
Arcsen

Service and channel teams at Gulf operators, distributors and cloud firms spend much of the day answering status questions. An enterprise customer’s IT manager asks whether a fault case is still inside its response time and when a new circuit goes live. A reseller asks whether a deal registration was approved, which price list is current and where an order is. A subscriber asks why this month’s bill is higher. The answers sit in the CRM, the order system and the billing platform, and people look them up by hand, in two languages.

Those questions suit AI agents, provided the records behind them are in order and people keep every decision that changes a contract or a bill. Our guide to Salesforce for telecom and technology companies covered the records. This one picks the first Agentforce agents to build on them, and the line each one must not cross.

Four agents worth building first

Enterprise service agent. For the IT contacts of enterprise customers, on the customer portal, WhatsApp and web chat. It opens fault cases with the site and service ID, reports where each case stands against its entitlement milestones, and gives order status for new circuits, licences and managed services. Major outages go straight to the network operations centre.
Partner and reseller agent. For reseller staff signed in to the partner portal on Experience Cloud. It answers deal registration questions from the channel rules and the partner’s own registrations, finds the current price list or datasheet the partner may see, and tracks orders and shipments.
Renewal assist agent. For account managers, inside Salesforce. Ahead of each end date it prepares a renewal brief: what the customer owns and when each asset ends, open cases and missed milestones, usage where billing shares it, and vendor price changes. Salesforce’s Summarize Record action works on a single record and cannot use Data 360 data, so a brief that spans assets, cases and usage needs a custom prompt template.
Consumer self-care agent. For subscribers in the app, on the website and on WhatsApp. It explains a bill line by line, shows usage, describes plans and roaming packs from approved content, and opens a billing dispute as a case.

Operators can start from the prebuilt subagents in Agentforce for Communications, Salesforce’s agent offering for communications service providers: Upsell & Cross-Sell, Quoting and Ordering and Site Grouping for sales, and Billing Resolution, Service Insights and Asset Service for service. Billing Resolution works from billing history, usage and network data, and Service Insights surfaces service level objective (SLO) insights on service commitments. Salesforce says these agents are built to make independent decisions in real time. For a first release in the Gulf, we draw the line tighter: the agent explains and prepares, and a person approves any credit.

Agent	Channel	Data and systems it needs	Actions it may take	Where a person takes over
Enterprise service	Customer portal, WhatsApp, web chat	Accounts, assets, entitlements and milestones, cases; order status from Revenue Cloud or the OSS	Open and update cases; report milestones and order status	Major outages, SLA credits, service and contract changes
Partner and reseller	Partner portal on Experience Cloud	Partner accounts, deal registrations, price lists, orders and shipments from the ERP	Report registration and order status; share permitted documents; open cases	Registration conflicts, special bid prices, MDF, credit limits
Renewal assist	Salesforce, for account managers	Assets and end dates, cases and milestones, pipeline, usage, vendor price lists	Prepare the brief; draft a renewal email for review	Price, discount, terms and sending the quote
Consumer self-care	App, website, WhatsApp	Verified subscriber; bills and usage from billing; plan content; cases	Explain bills and usage; describe plans; open a dispute case	Credits, disputes, contract changes, cancellations, SIM swaps, number transfers

What the agents need

The records first. Each agent reads what the org already holds: assets with term dates, entitlement processes, partner registrations and orders. Fix gaps there before you build. Bills, usage and network orders stay in billing and the OSS, read through MuleSoft with only the fields an answer needs.
Portal access is the guardrail. On Experience Cloud, signed-in users run the agent under their own profile, permissions, field-level security and sharing rules, and Salesforce says context variables identify a user without granting access. A reseller sees only what its portal user may see, so test partner sharing before the agent. Unidentified visitors and customers verified in chat run as the agent user, so keep its access narrow. When you add chat to the site, Trailhead says to put the site domain on the CORS allowlist, or the chat window will not load, with no obvious error.
Verification for subscribers. Salesforce’s standard customer verification emails a one-time code and keeps private subagents (Salesforce’s current name for topics) locked until it matches. An operator will usually want the code sent to the mobile line, which means overriding the verification flow, as Salesforce allows.
Knowledge in both languages, with owners. The knowledge retriever drops articles whose language differs from the conversation’s, Salesforce’s multi-language guide explains, and an uploaded file answers in its own language: an English price list PDF answers Arabic questions in English. Give plan, roaming, channel, SLA and billing articles one owner each, in Arabic and English, in line with the plan pages in our guide to telecom websites on SitecoreAI.

Guardrails and handover

Handover runs through the Escalation subagent, which moves the conversation and everything gathered to a queue or rep by an outbound Omni-Channel flow, and makes one attempt per session. Route enterprise conversations to the account’s own service team and partner conversations to the channel manager, and add the Check Availability for Routing element so that, when nobody is free, the agent opens a case with the Create Case with Enhanced Data action. Give that case its entitlement, so the SLA clock starts at once.

What stays with people. Contract changes of any kind: upgrades and downgrades with new commitments, early termination, renewal terms and price. Credits, bill adjustments and refunds. Billing disputes and SLA credit claims. Deal registration conflicts, special bid prices, MDF approvals and credit limits. SIM swaps, number transfers and changes of ownership. Cancellations and retention offers. The agent explains, gathers the facts and opens the case; a named person decides.

Testing and measuring, before and after launch

Run Testing Center only in a sandbox, as Salesforce advises, because tests can change CRM data, and point it at test billing and order data. Generate tests from the agent’s subagents, actions and knowledge, upload your own from real transcripts, and review scores on measures such as completeness, coherence and instruction adherence. Salesforce labels the Agentforce Studio version of Testing Center as Beta.

Salesforce’s language support page marks Arabic as Beta for service and employee agents. Test Gulf Arabic, English and mixed messages, plan and brand names in both scripts, and partner terms such as deal registration and special bid. For the portal, sign in as users of two resellers and check that neither sees the other’s registrations, orders or price lists.

Once live, Agentforce Observability shows each session down to the subagent and turn, groups conversations by intent and gives each a quality score. Measure from your own baseline, by language and audience: containment for status questions, handover quality, complaints about the agent, cases opened with every detail the SLA clock needs, and disputes reopened.

Our work with telecom and technology companies

Brother’s UAE distributor channel runs self-service on a partner portal, with omni-channel customer service on one desk. Our telecom and technology clients include Mindware, CNTXT and Qatar Computer Services, and at LEAP 2026 in Riyadh we signed a partnership agreement with Mannai Information Technology Saudi Arabia.

Where to start

Count last quarter’s contacts by reason, audience and language, and mark the status questions your records can already answer.
Pick one audience first, enterprise customers, resellers or subscribers, and write the agent’s job, data, actions and handover rules on one page.
Fix the records it reads: assets with end dates, entitlement milestones, partner sharing and orders.
Agree the credit, dispute and contract rules with finance, legal and the account teams, and build them into the instructions and the escalation flow.
Test in a sandbox in both languages and as two resellers, then launch with a staffed queue and review session traces weekly.

Choosing your first telecom agent? The free Agentforce Readiness Assessment takes ten working days: it picks three use cases, checks the data and permissions they need, and gives you a costed pilot plan. See our telecom and technology work, or talk to our telecom team.

Frequently asked questions

Does Salesforce offer prebuilt AI agents for telecom?

Yes. Agentforce for Communications lists prebuilt subagents for upsell and cross-sell, quoting and ordering, site grouping, billing resolution, service insights and asset service, aimed at communications service providers.

Can resellers use an AI agent inside the partner portal?

Yes. A service agent can run in an Experience Cloud site through enhanced chat, and signed-in partner users run it under their own permissions and sharing rules, so a reseller sees only its own records.

Should an AI agent approve bill credits?

We advise against it in a first release. Let the agent explain the bill, gather the facts and open the dispute case, and keep credits, disputes and contract changes with a named person.

Does Agentforce support Arabic for telecom customers?

Arabic is available with a Beta label for service and employee agents. Because the agent only retrieves knowledge in the conversation’s language, plan, roaming and billing content needs Arabic versions, tested before launch.