Use AfriRoute AI as documented developer capability, not vague platform branding
The developer portal should explain where AI is used in real developer workflows: routing, chatbots, provider integrations, observability, and grounded documentation support.
Docs mode
Reference and guide
Keep the task clear, the example nearby, and the next step obvious.
Documented AI surfaces
Developers should see AI where they can actually use it
Keep this section operational and developer-facing. Show endpoints, payload patterns, workflows, and limits. Do not turn AI into generic platform copy without implementation guidance.
Start from the real jobs
AI Routing
Explain how delivery probability, latency, route health, cost, and fraud-aware signals guide operator selection.
AI Chatbots
Show bot creation, channel connection, webhook handling, and where model-backed responses fit into the flow.
AI Provider Integrations
Document how teams configure providers, model choices, completion services, and safe fallback behavior.
AI Assistant
Keep the docs copilot grounded in the same public sources the rest of the portal uses.
AI assistant rules
Suggested AI assistant prompts
How does AI routing work?
Use the AI routing docs to understand how delivery probability, latency, route health, fallback readiness, and fraud-aware signals influence route choice. Then inspect the result through routing decisions, routing insights, network coverage, and delivery performance pages.
How do I build an AI chatbot?
Create a bot, connect the supported channel, attach webhook behavior, then configure the AI provider and model. Start from the AI Chatbots page and connect it back to WhatsApp, contact center, or webhooks depending on the flow.
How do I connect OpenAI or another model provider?
Use the AI provider integration surface to configure providers, models, and completion behavior without separating AI from your messaging, bot, or support workflow. Keep provider setup near the channel or webhook flow that consumes it.
How does AfriRoute route messages across operators?
Use the network and performance docs to understand how AfriRoute routes through channel-specific connectors while monitoring delivery rate, latency, retries, and carrier health.
Which carrier route is healthiest?
The performance surface should show route health by carrier and country using delivery rate, latency, route failures, and traffic volume so developers understand how AfriRoute optimizes delivery.