Ask for artifacts, not adjectives
Request an anonymized handover template, a sample voice guide using fictional content and the weekly report definitions. A provider should be able to explain how those documents are used.
Ask who covers an absent operator and who can stop a campaign. If every answer is “our system handles it,” you still do not know who is accountable.
| Ask for | Look for |
|---|---|
| Written quote | Fee base, coverage, notice and exclusions |
| Access plan | Platform-specific permissions and revocation |
| Review rubric | Voice, accuracy, boundaries and disclosure |
| Sample report | Denominators, net/gross basis and time period |
| Case study | Permission, source records and traffic context |
| Exit checklist | Open requests, access removal and data handling |
Check proof without demanding private fan data
A valid result needs a period, baseline, metric definition and permission to publish. Screenshots with no dates or attribution are insufficient. Agency-wide revenue does not prove a chat-specific increase.
A provider should not expose another creator’s private conversations to win your business. An anonymized report with permission is more useful than a folder of unredacted chats.
Watch for these red flags
- Guaranteed earnings or universal revenue multipliers.
- A request for passwords before fit and scope are discussed.
- No written explanation of refunds, attribution or cancellation.
- Claims that fans can never tell a team is involved.
- AI compliance claims without a current primary policy source.
- Refusal to explain how account access ends.
Agree a pilot and a stop condition
Define the coverage, evaluation period and review meeting before starting. Compare quality and queue measures alongside sales, and record traffic or content changes that affect the result.
Use the same checklist for Bambi. The pricing page identifies the missing public chat-only rate, and the results page labels the case-study evidence still needed.
Start with a scope discussion