Automation: Kepler

Automate recurring work

Workflows take handgrips off you that someone would otherwise do manually, and make sure they happen reliably instead of getting lost in daily business. And that without developers: you assemble them yourself.

Triggers and steps

A workflow starts at an event (a deal changes stage, a new contact is created) and then runs steps: set a status, create a task, trigger an email. “Someone should do that” becomes “that happens automatically”.

An example

New lead via the contact form → status “new”, task “call within 24 h” for the responsible salesperson, confirmation mail to the prospect. Set up once, it runs equally reliably for every lead.

Reliable in the background

Execution runs in the background, is safeguarded against double execution and retries on errors. So the steps happen reliably, without anyone having to think of it or sit in front of it.

Forms as triggers

Automations also react to forms: the “form submitted” trigger starts, for example, an automatic confirmation to every new prospect, optionally only for a specific form, with all form fields available as text building blocks. On its card, every automation shows when it last ran and whether runs failed: you see at a glance that it’s alive.