Workflows

A workflow is a rule of your program that Introw enforces for you. It watches for something happening to a partner, checks whether it is the case you care about, waits if it should, and acts. You define it once by picking from a list, and it runs the same way for every partner, however many you have.

​

The problem it solves

Most programs already know their rules. The cost is enforcing them by hand, for every partner, every time.

​

Impact

A partner cannot tell whether your program is well run until something is late. Workflows keeps it from ever being late, at fifty partners or five thousand, with the same team.

​

See it work

​

How it works

Every partner program runs on a handful of rules, and most of them are already written down. When a partner certifies, move them up a tier. When onboarding finishes, pay the sign-up bonus. When a task is about to be late, remind the partner, and if it goes late anyway, tell the partner manager. When a field changes on the partner’s account in the CRM, put them on a different portal experience. The rules are not the problem. Enforcing them is. Each one has to be remembered and carried out by a person, for every partner, every time it applies. At twenty partners that is a checklist. At two hundred it is a job, and the usual answer is another partner manager. Workflows turns each rule into something Introw does on its own, every time it applies. You start from a trigger. A task assigned or completed. A partner or contact created or updated. A form submitted, or a submission accepted, declined or returned. A journey or a course started or finished. A certificate earned. A deal or other CRM record linked to the partner changing. A partner entering or leaving a segment. You narrow it, so the workflow only runs for the partners and the events you actually mean. Then you lay out what happens. Write fields on the partner, move them to another portal experience, add them to a segment, or enroll them in a journey. Give them or your own team a task, issue a certificate, or book a commission line. Email their contacts, post a Slack or Teams nudge, or log a note on their CRM record. Every note, task, email and message can name the partner, the event and what the steps before it did, so it reads as if someone wrote it for that partner. Between those actions you can wait and you can branch. A wait can be a plain pause, or it can be anchored to a due date. That is what makes “three days before it is due” and “two days after it was due” expressible at all. A branch splits the flow in two, so one workflow covers both the partner who did the thing and the partner who did not. Nothing goes live by accident. A workflow saves as a draft, Introw tells you exactly what is still unfinished, you rehearse it against one real partner without writing anything, and only then do you switch it on. Every run afterwards is logged and painted back onto the same canvas, so you can see which path a partner took. Because the rule is defined once, it is applied the same way to every partner. Same trigger, same conditions, same outcome, whether it fires once a month or two hundred times a day. No partner is tiered up late because their manager was on holiday, and no two partners get a different answer to the same situation. That consistency is what lets a program grow without the team growing with it. More partners means more runs, not more people. Instead of a partner manager holding a checklist and a calendar of follow-ups, the program enforces itself. Introw acts on the moment worth acting on. The partner hears from you at the right time, on the right channel. The record is updated on both sides. And the manager is pulled in only when a human is genuinely needed.

​

Going deeper

Works with