Purpose and location
Apply rate cards and account codes to produce explainable usage costs.
Open Insights → Billing. The available controls depend on the active edition, module entitlement, role and tenant scope.
Before you start
Start with the narrowest tenant, participant and time range. Access to call evidence may expose personal data and must follow the assigned role and retention policy.
Capture the current value or export the affected records before a bulk or routing change. This gives the operator a precise comparison point and makes a supported transaction undo easier to assess.
Step-by-step workflow
Complete the steps in order. Do not combine an initial configuration with unrelated cleanup; small, attributable changes are easier to test and reverse.
- Import and validate a versioned rate card.
- Assign it to the correct tenant or plan.
- Run a preview before closing a period.
- Export rated details and totals.
Field reference
Use the reference below while completing the form. Fields hidden by edition, module entitlement or role are intentionally unavailable to the signed-in user.
- Prefix
- Longest-prefix destination match.
- Setup charge
- One-time charge per answered call.
- Rate
- Per-minute or billing-increment price.
- Effective date
- Version start for a rate card.
- Account code
- Grouping key for cost attribution.
Acceptance checks
A saved record is only the beginning of validation. Run every relevant check below and retain the call-session ID, time and result when telephony is involved.
- Find one known call or record by exact time and participant.
- Verify an unauthorized role cannot view or export the same evidence.
Common mistakes and safe recovery
If a check fails, stop adding changes. Restore the previous value or use a supported transaction undo, regenerate PBX configuration, then repeat the smallest failing test.
- Call details, recordings and packet captures can contain personal or confidential communications.
What to include in a support case
Provide the tenant, module and object name, local time with timezone, expected result, observed result and the most recent successful state. For a call problem, include the logical call-session ID and the redacted SIP/SDP text diagnostic before requesting PCAP.
Never paste passwords, private keys, raw license payloads or unredacted customer media into a ticket. Use the one-time diagnostic grant and attachment controls when support requests additional evidence.