Make the campaign brief usable across a team
A South Africa-focused project can involve several languages, accounts and people preparing the content. Keep a short written brief for each target: platform, public address, intended metric and any audience requirement. The panel’s service description defines delivery conditions, while the team’s brief defines why the order is being considered.
A handover should not rely on a screenshot of a service name alone. Record its ID and recheck its current price and limits before submission. If a teammate changes the target post or profile address, update the order plan before anyone continues with an older link.
Source: DataReportal Digital 2026: South Africa. These are dated market estimates, not live service inventory. Social media identities are not necessarily unique people.
Example: an agency managing several client profiles
Imagine an agency preparing a campaign for two clients with similar profile names. Keep separate target records and verify the account visible at each URL before ordering. Match the requested service to the exact metric for that client, calculate the charge and save the resulting order ID. When reviewing progress, use the relevant order record rather than a shared total across clients. This keeps later questions about quantity, conditions or delivery attached to the right task.
- Keep client records and public targets distinct.
- Recheck the service ID after a team handover.
- Treat language requirements separately from geography.
Give each team member the same campaign identifiers
For a South Africa agency working across several client accounts or languages, the main ordering challenge is often keeping the asset and service specification intact during handover. Save the public link, platform, metric, current service ID and intended quantity together. A campaign nickname alone is not a service target.
An English video and a separately published local-language version are distinct assets. Subtitles or a caption edit on one upload do not automatically create another target. Check the actual addresses before ordering, and do not infer South Africa coverage from the creator’s location.
| Decision | Check in the brief or service |
|---|---|
| Client brief | Audience requirement, language and business purpose. |
| Order handover | Exact link, service ID, quantity and current conditions. |
| Monitoring handover | Returned order ID and latest status. |
| Client report | Delivered metrics separately from enquiries or sales. |
Hand over two client profiles without losing ownership of the records
For a ZAR quote, retain the client price separately from the account currency, final service charge and any conversion. A teammate should check the existing order outcome before resubmitting after a timeout or a delayed counter. API credentials belong in the integration’s protected configuration, not the client spreadsheet.
| Handover field | Client A and Client B need separate entries |
|---|---|
| Destination | Client name, exact public URL and the account visible at that URL; similar profile names are insufficient |
| Order specification | Platform, requested metric, service ID and permitted quantity for that client |
| Follow-up | Returned order ID, current status and the teammate responsible for review; do not combine both clients into a shared counter |
Before you submit an order
The account and order process is the same across these country guides. Use this checklist with the local campaign notes above.
Match the service to the target
Choose the platform, metric and service ID. A profile, post, video and invite link are different targets. Use the selected service’s required format and extra fields; keep the target accessible and its address stable while processing. Never provide a social media password or recovery code.
Compare the actual conditions
Check audience and language coverage, quantity limits, start conditions and after-order support. Average delivery time is not a deadline. Refill eligibility and its request window do not establish permanent retention or cancellation rights. Resolve any essential condition missing from the description before ordering.
Check the estimate and account charge
For a rate per 1,000, the estimate is rate × quantity ÷ 1,000; other pricing units may work differently. Keep currency conversion and payment-provider fees separate. Sign in, review the methods in Add funds and confirm the final native order charge. A public estimate or Continue button does not place a paid order.
Keep an order record
After confirmation, save the target, service ID, quantity and order ID. Follow the status before repeating an order or opening a support request. API clients should check an uncertain outcome before retrying and keep credentials private. Report the purchased metric separately from sales, audience interest or platform eligibility.
For the full walkthrough, read the service and order guide, API documentation or account and support FAQ.
Questions before choosing your service
What should a South Africa agency include in an order handover?
Can a campaign nickname replace a public URL?
Do subtitles create a second target?
Does a South African creator account guarantee local delivery?
Should another team member retry an uncertain API submission?
Can the client report combine views and followers into customers?
Does a country page establish a local billing currency?
How should I compare a low SMM panel price?
Does a completed order prove a business result?
What should I preserve for order support?
For account and order help, search the support FAQ.
Choose your next service.
Review the target, quantity and conditions before continuing.
Estimate your order