Compare your Batch push and email campaigns, from Claude or ChatGPT
Which campaign performed best, where unsubscribes come from, how a recurring one evolves: Batch statistics in your AI, with no Batch account.
Published on October 28, 2026
In short
- Connect your Batch project to your assistant through Persyst: it lists orchestrations and compares their statistics day by day.
- A founder, an agency or a product manager follows campaigns without opening Batch or having an account there.
- Read-only: no campaign created, sent or stopped from the assistant.
Which push campaign performed best this month, and which one drove away the most subscribers?
Best campaign: “New season” on October 14, 18.4% open rate on 312,000 sends, against 11% on average this month. Most unsubscribes: the recurring “Cart reminder” on Thursdays, 0.9% per send against 0.3% for the others. It goes out four times a month to the same users: I would look at its frequency.
Sources consulted
- Batch · orchestrations · October
- Batch · statistics per orchestration
The problem: numbers in a tool few people open
Campaign results matter to leadership, product, the agency. But Batch is opened by the CRM team, and everyone else waits for an export or a screenshot. Comparing two campaigns, or following a recurring one over three months, means browsing orchestration by orchestration.
What the assistant does, step by step
With Persyst’s Batch connector, the question “Which campaign performed best this month?” chains:
- List the project’s orchestrations, filtered by type or status (
list_batch_orchestrations). - Read each one’s statistics over the period: sends, opens, clicks, unsubscribes, conversions (
get_batch_orchestration_stats). - Compare and rank, then point at the anomaly: an unsubscribe rate too high, a recurring campaign running out of steam.
Three questions to try
- “Compare iOS and Android push open rates on Tuesday’s campaign.”
- “How has the recurring newsletter’s click rate evolved since July?”
- “Which triggered orchestrations have the best conversion rate this quarter?”
Setup
- An administrator connects the Batch project with its API key (Batch guide).
- They open the project to the team, client or person following the campaigns.
- Each member adds Persyst to their assistant (getting started).
Limits to know
- Read-only: no campaign created, scheduled, sent or stopped.
- No profiles, audiences or message content: only orchestrations and their metrics.
- Six months of history at most per query.
Questions
Frequently asked questions
Does each person need a Batch account?
No. An administrator connects the Batch project once with its API key. Authorized members look at campaigns from their AI, with no Batch seat.
Can a project be opened to an agency?
Yes. You grant this project to this agency or person, and only this one. Other projects stay invisible to their assistant.
Does the assistant see user profiles?
No. Only orchestrations and their statistics are read: no profiles, no audiences, no message content.
Over which period can I compare?
Up to six months of history per orchestration, day by day, with a per-platform breakdown if you ask for it.