What is Save as Template in OniHelper? Save as Template is the OniHelper Suite pattern that lets you store a configuration you’ve built up and dialed in — schedule allocation, tool settings, whatever the tool exposes — and reload that stored configuration later against new devices or new account sets. Instead of reconfiguring the same values every time you provision a new phone or onboard a new client’s accounts, you save the config once, name it, and pull it back when you need it. Standard across most OniHelper modules.
Where it shows up
Time Manager is where operators encounter Save as Template most often. You set up a Round-Robin schedule with your preferred runtime window, rounds per day, and minimum runtime — spend time getting it right — and save the whole thing as a template. Next time you provision a new device, Import Template pulls those settings back in one click.
The pattern appears in other Suite tools too. Post Scheduler workflows can save their scheduling configs. Copy Settings inside Threads Manager preserves Follow-tool tuning as reusable templates. The specific UI varies per tool, but the concept is consistent: save what took time to build, reload it when you need it again.
Why templates matter at fleet scale
Fleet operators who don’t use templates end up doing the same configuration work over and over. New phone arrives → open Time Manager → set the runtime window → pick Round-Robin → configure rounds per day → set minimum runtime → apply. Every phone. Every time. Same values, same clicks, same time cost per device.
With templates, that whole flow collapses to two clicks: Import Template, then Apply. Whatever you would have configured manually gets loaded from the saved config. Time per device drops from minutes to seconds, and — more importantly — the configuration is identical across devices because it’s coming from the same source. Manual configuration drifts over time as operators forget exactly what values they set last month; template-based configuration doesn’t drift because the values live in one place.
How to use it well
Basic workflow:
1. Get the config right once. Spend real time tuning your Time Manager settings on one device. Round-Robin with 4 rounds per day, 30-minute minimum runtime, 08:00-22:00 window. Test it, verify accounts run cleanly, confirm it doesn’t produce parallel-execution overlaps.
2. Save it with a name that means something later. “template-1” tells you nothing in six months. “5-accounts-per-device-warmed” tells you what the template’s for. Name templates for the specific fleet configuration they fit.
3. Import when you provision new devices. Open Time Manager on the new device, click Import Template, pick the right one, click Apply. Done.
4. Maintain the template as you learn. If you discover your original settings weren’t quite right — say the runtime window needs to be different — update the template rather than editing individual devices. Then next time you Import, you get the improved version. Individual devices already provisioned with the old template need to be re-imported manually to pick up changes, which is a manual per-device operation Save as Template doesn’t automate away.
What templates don’t cover
Save as Template stores tool-level configuration, not per-account data. Templates don’t include specific account usernames, per-account tags, or any data that’s unique to individual accounts. They store the configuration values (timing settings, allocation methods, tool parameters) that apply the same way across every account you use them with.
This is the right scope. If templates included per-account data, they’d become useless for their actual purpose — you’d get somebody else’s usernames and tags every time you imported. The scope keeps templates portable and reusable across arbitrary device sets.
Template hygiene at agency scale
Agencies running multiple clients typically maintain a small set of standard templates that map to their operational tiers — one for warm-up accounts, one for warmed accounts, one for high-volume operations, one for specific client requirements. New device provisioning becomes a template-selection exercise instead of a configuration exercise. The specific benefit isn’t just speed — it’s consistency across the fleet, which makes debugging easier because every device with the same template behaves the same way.
Operators who accumulate dozens of templates over time (one per campaign, one per experiment, one per client at each stage) usually discover they only use a handful regularly. Periodic cleanup — delete templates that aren’t in use, rename the ones you keep so their purpose is obvious — keeps the template list manageable.
Related Terms
- Time Manager — The OniHelper Suite tool where Save as Template appears most prominently
- OniHelper Suite — The parent application that exposes the Save as Template pattern across multiple modules
- Copy Settings — The parallel bulk-configuration pattern that propagates settings across accounts rather than across devices