Using Buzz for Help and Actions

Buzz is the assistant built into the WARP portal. It can answer workflow questions, explain what you are seeing, help fill supported forms, search customer-safe guides, and prepare certain changes for confirmation.

Buzz follows your active customer and your permissions. It should not expose data from another customer, and it cannot perform an action unless your role has the required scope.

Asking Questions

Use Buzz for questions like:

• "How do I set up a SIP trunk?"
• "Why can I not assign this number?"
• "What does this port status mean?"
• "Which scope do I need to create an API key?"
• "How do I fix one-way audio?"
• "Why is my campaign rejected?"

Buzz retrieves guidance from WARP customer guides and uses your current page context when available. If you are on a trunk, number, campaign, or port request page, ask with that context in mind.

Form Filling

On supported pages, Buzz can prepare form values from your request. For example, it may help fill a trunk form, number search, or campaign registration fields.

Form filling is not the same as submitting. Review the values before saving. Buzz should never ask you to blindly accept a change. If the values are incomplete or you are unsure, correct them manually or ask a follow-up question.

Confirmed Actions

For changes that modify your account, Buzz prepares a pending action and asks you to confirm. Some actions also require step-up verification.

Examples of write actions that require the relevant feature scope:

• Assigning or routing numbers requires numbers:write.
• Creating or updating trunks requires trunks:write.
• Editing port requests requires porting:write.
• Submitting, activating, canceling, or supplementing ports requires the matching porting action scope.
• Managing campaigns requires messaging:campaigns:write.
• Creating or rotating API keys requires api_keys:write.

Buzz itself uses buzz:write for confirmed action execution, but the underlying feature scope still matters. Having Buzz access does not bypass normal permissions.

File Uploads and Batch Work

Where supported, Buzz can inspect uploaded files or run batch-style actions. Upload only files relevant to the current task. Do not upload secrets, unrelated customer data, or documents you would not normally share with support.

Batch actions should be reviewed carefully before execution. Large changes can affect many numbers, campaigns, or records at once.

Feedback and Learning

Use thumbs-up when Buzz gives a useful answer. Use thumbs-down and add a correction when the answer is wrong, incomplete, or unclear.

Feedback helps improve future assistance. Corrections may be reviewed before they become reusable guidance. Do not put secrets, passwords, API keys, or private unrelated data in feedback text.

What Buzz Should Not Do

Buzz should not provide legal approval, tax advice, or regulatory sign-off. It can explain what the portal asks for and why, but for legal or compliance conclusions, involve the appropriate expert.

Buzz should also not invent portal behavior. If a surface is not fully self-service, Buzz should say so and help you gather the right information for support.

Scopes and API Reference

Buzz conversation and feedback use buzz:use:

• POST /v1/buzz/ask
• POST /v1/buzz/ask/stream
• GET /v1/buzz/sessions
• GET /v1/buzz/sessions/:id/messages
• POST /v1/buzz/sessions/:id/continue
• POST /v1/buzz/sessions/:id/end
• POST /v1/buzz/feedback/:turnId
• GET /v1/buzz/suggestions

Confirmed actions and batch execution use buzz:write and may require step-up:

• POST /v1/buzz/execute
• POST /v1/buzz/pending/:id/cancel
• POST /v1/buzz/upload
• POST /v1/buzz/batch/execute
• GET /v1/buzz/batch/:id/progress