Campaign setup and reporting checks
Use the same source-filter-limit-review pattern for each client, then inspect results campaign by campaign.
For agencies
Every client gets its own campaigns, its own posting schedule and its own daily ceilings — but you run them from one workspace, and every action is logged against the account that made it.
Up to 7 X accounts on Scale · 1,500 daily activities · Priority queue
Accounts are isolated by design. Switching from one client to the next swaps the campaigns, the queue, the schedule and the limits with it — there is no shared state to leak a template into the wrong brand’s timeline.
When a client asks what you did last month, you should not be reconstructing it. Twifly records each follow, like, repost, reply and DM against the campaign and account that produced it, with a link back to the post it touched.
7 core automations + Auto DM per account, up to 56 campaigns including paused.
Daily activities across the workspace, with priority queue.
Plus 50 new Bulk Outreach / DM Sequence campaigns a month. Daily sending limits still apply.
Campaign access and advanced actions follow each plan's permissions.
Repeatable client operations
Standardize how a campaign is configured and reviewed while keeping each connected X account’s campaigns, queue, schedule, limits, and activity in its own context.
Use the same source-filter-limit-review pattern for each client, then inspect results campaign by campaign.
Switching account context changes the campaigns, posting schedule, action limits, and activity you are reviewing.
Twifly supports multi-account workflows; this page does not promise unbuilt roles, client portals, or collaborative approvals.
Agency questions
Yes. Connected accounts keep their campaign, queue, posting-schedule, and limit context separate when you switch between them.
Those capabilities are not claimed here. The current agency use case is multi-account operation and repeatable workflows, not an unbuilt collaboration layer.
Twifly exposes dated activity and campaign-performance reporting. Review the exact data available for the account rather than promising outcomes before activity exists.
No. Per-action caps, schedules, and filters control the configured workflow, but the operator remains responsible for following current X rules and recipient expectations.
One workspace, every account, one log you can actually send.