Skip to main content

Pipeline Assistant

Keep your sales pipeline accurate automatically. Pipeline Assistant checks your Cinode projects against rules you define and messages the right person through the Chat Agent in Slack or Microsoft Teams.

Written by Magnus Burton

Pipeline Assistant keeps your sales pipeline accurate on its own. It watches your Cinode projects, checks them against rules you define, and messages the right person when a deal is missing information, has gone quiet or needs a status change. It can also move a project to another stage or change its status for you. Nobody has to run manual pipeline reviews or chase colleagues for updates.

Pipeline Assistant delivers its messages through the Cinode Chat Agent, so they arrive in Slack or Microsoft Teams next to your other Cinode chats. You read the message, click the link and fix the deal in Cinode. You install and set it up yourself in Cinode Flows. Everything happens inside Cinode.

To receive notifications, the Chat Agent must be set up for your workspace. Without it, notification rules still save, but nothing is delivered. Rules that move a project or change its status work without the Chat Agent.


What Pipeline Assistant does

Pipeline Assistant runs a set of rules against your projects and acts on them automatically. This is what it can do for your team.

Pipeline Assistant mascot

Checks your deals against your own rules

When someone updates a project, Pipeline Assistant checks it in real time against the rules for that pipeline stage. If required information is missing, for example no deal value, a close date in the past or roles without a rate, the person who made the change gets a message listing exactly what needs fixing, with a link to the project. Each item carries an icon for its severity: error, warning or info.

Acts on deals that have gone quiet

Every night at 06:00 UTC, Pipeline Assistant looks for open projects that nobody has touched for longer than the number of days you set. Depending on the rule, it notifies the deal's sales managers, moves the project to another stage, or changes its status. A stale deal is flagged once when it first crosses the limit. It is not flagged again until someone works on the project and it goes quiet again.

Sends a weekly pipeline digest

Every Monday at 09:00 in Swedish time (Europe/Stockholm, so CET in winter and CEST in summer), each recipient gets one summary of all their projects that still have open items. The digest covers notification rules that use the "project is updated" or "inactive for N days" trigger, for open projects. A recipient with nothing outstanding gets nothing. The section on the weekly digest below has the details.

Lets you drive the pipeline from chat

Managers can ask the Chat Agent to move a project to a stage, set its status, undo a stage move or run the digest now. Any user can subscribe to pipeline-issue alerts. See Pipeline Assistant: Use it from chat.


How rules work

Everything Pipeline Assistant does is driven by rules you define. Every rule follows one pattern, when, if, then. When something happens to a project in the stages you choose, if the conditions are met, then Pipeline Assistant takes an action. A Cinode administrator sets up the rules per pipeline in the configuration wizard.

When: the trigger

The trigger decides when a rule is checked, together with the stages you attach it to. A rule needs at least one stage. There are five triggers:

  • When a project is updated. Checked in real time every time someone saves an open project, whichever field changed. This is the trigger for validation notifications.

  • When a project enters the stage. Checked in real time when an open project moves into one of the stages. A newly created project counts as entering its first stage.

  • When a project has been inactive in the stage for N days. Checked every night at 06:00 UTC. A project is inactive when its last activity in Cinode is at least N days old. The number of days must be 1 or more. A project without a last-activity date is never treated as inactive.

  • When a project's status changes. Checked in real time when a project is set to Won, Lost, Abandoned, Suspended or reopened. This is the only trigger that also applies to projects that are no longer open.

  • When a role on the project is assigned, booked or changed. Checked in real time when someone creates a role, assigns or removes a person, or adds, removes or changes a preliminary booking on an open project. Deleting a role does not trigger rules.

If: the conditions

Conditions decide whether the rule acts. A rule can have any number of conditions, and all of them must be true together. There is no "or" and no "not". A rule with no conditions always acts when its trigger fires.

Conditions work in one of two ways, and the name tells you which:

  • Completeness conditions match when something is wrong. For example "Deal value missing or too low" matches a project that has no deal value. A notification rule with this condition tells you which deals are missing a value.

  • Scope conditions match when something is true. For example "Team is" matches projects that belong to the team you chose. Use them to limit a rule to some projects. "Roles staffed" and "Roles are within area" also match when something is true.

The table lists every condition, when it matches and what you can set on it.

Condition

Matches when

What you can set

Deal value missing or too low

The estimated value is empty, zero, or not greater than your minimum.

Minimum deal value, default 0. Leave at 0 to only require that a value is set. Compared in the project's own currency, with no conversion.

Contract value missing or too low

The contract value is empty, zero, or not greater than your minimum.

Minimum contract value, default 0.

Estimated close date missing or overdue

No close date is set, the date is in the past, or optionally it is further away than your limit. Today counts as not overdue.

Maximum days from now, 0 or more. Leave blank for no upper limit.

Probability missing or too low

No win probability is set, or it is below your minimum.

Minimum probability from 0 to 100 percent, default 0.

No roles created

The project has no roles.

Nothing to set.

Roles not assigned

At least one role has no assigned person. The message names each role.

Nothing to set.

Roles not preliminary booked

At least one role has no preliminary booking.

Nothing to set.

Roles missing a rate

At least one role has an empty rate or a rate of zero or below.

Nothing to set.

Roles staffed

Enough roles are staffed. A project with no roles never matches. Pairs well with the role trigger, for example to set a project to Won once it is staffed.

Counts as staffed is required with no default: Assigned, Preliminary booked, or Assigned or preliminary booked. Minimum staffed roles is a number from 1, and blank means every role.

Owner team missing

The project has no owner team.

Nothing to set.

Description missing

The description is empty or only spaces.

Nothing to set.

Status reason missing

The project has no status reason. Pairs well with the status-changed trigger and "Project status is", for example to remind someone who marked a deal Lost to say why.

Nothing to set.

Project status is

The project's current status equals the one you choose.

Status: Open, Won, Lost, Abandoned or Suspended. Required.

Team is

The project belongs to the team you choose.

Team. Required.

Manager is

The person you choose is a sales manager or project manager on the project.

Person. Required.

Custom field is

One of your project custom fields matches the comparison you set.

Text fields: has a value, equals, begins with, contains. Number fields: has a value, equals, is larger than, is smaller than. Dropdown fields: has a value, is, is not. The field and the comparison are always required. A value, or an option for a dropdown field, is required for every comparison except "has a value".

Roles are within area

The project's roles are in one of the listed countries or within the radius of one of the listed places. Use it with "Move to stage" to route requests by location. See "Route requests by location" below.

Countries, picked from Cinode's country list, one row per country. Leave empty to use places only. Places, cities or areas such as Stockholm or Göteborg. Leave empty to use countries only. Places use a Google Places connection that Cinode has already set up. Radius (km), the distance around each place, default 50 and maximum 2000. Roles that must be inside: All roles that have a location (the default, roles without a location are ignored), Any role, or The first role.

Important: The minimum deal value, contract value and probability are floors. They flag values that are too low, never too high. To target high-value deals, use a number custom field with "is larger than" instead.

Then: the action

The action is what happens when the trigger fires and the conditions match. There are five actions:

  • Send notification. Messages the recipient you choose, with the items found. You set a severity and an optional custom message.

  • Move to stage. Moves the project to a stage you choose. The stage can be in another pipeline.

  • Set project status. Sets the project to Open, Won, Lost, Abandoned or Suspended.

  • Revert to previous stage. Puts the project back in the stage it came from. It is available only with the "enters the stage" trigger.

  • Revert to previous status. Puts the project back to its previous status, including Open. It is available only with the "status changes" trigger.

A notification works with all five triggers. Moving a project, setting its status and the two reverts cannot be used with the "project is updated" trigger. Reverting does nothing when there is no earlier stage or status to return to. If several rules change one project from the same event, the changes are combined into one update, and the rule listed last wins.

When a rule moves a project to another stage, your "enters the stage" rules for the new stage run as well, as if a person had made the move. This chain stops after 5 moves in a row. Status-change rules run after a status change made from chat or by a role rule, but not after a status change made by a nightly rule or an "enters the stage" rule. A project that a rule has set to Won is no longer checked by role or update rules, which prevents loops.

Route requests by location

The "Roles are within area" condition routes each request to the pipeline for its region. You add one rule per destination, with the "enters the stage" trigger on your intake stage and the "Move to stage" action. For the exact settings, see Route requests to a regional pipeline by location.

A rule with this condition waits for role locations before it checks them. For projects that Inbound creates, it runs as soon as Inbound has added all roles. For projects created any other way, it waits until every role has a location, for up to 3 minutes, and then checks.

If a place cannot be found, a role location cannot be read, or no role has a location, the condition does not match. The project then stays in the intake stage for a person to handle. If the project is deleted, closed or moved during the wait, nothing happens.

Who receives a notification

For a notification rule you choose who gets the message:

  • The person who made the change. This is the default.

  • Sales managers. The project's sales managers.

  • Project managers. The project's project managers.

  • Specific people. One or more colleagues you pick. At least one is required.

  • A channel. A shared chat channel. This option appears only when the Chat Agent is connected and has a channel list, which is currently available for Slack. Private channels are marked "(private)".

If there is no person who made the change, the message goes to the project's sales managers instead. This happens in every nightly check and in the weekly digest, and when the change came from a source with no email address. In real-time checks, each recipient gets one message per event, combining the items from all matching rules. In the nightly check, each rule sends its own message.

People are matched to their chat account by email address. A person with no email in Cinode, or whose Cinode email does not match their Slack or Teams email, is skipped and not told. A rule that ends up with nobody to notify sends nothing.

What a notification contains

Every message links to the project with an Open project in Cinode button. The title depends on the trigger and the rule:

  • A validation message reads "N issue(s) found on" followed by the project name.

  • A rule with no conditions reads "Pipeline notification for" followed by the project name, with the rule's message or name as the text.

  • A status change reads "status changed to" followed by the status.

  • A role change reads "Roles updated on" followed by the project name.

  • The weekly digest reads "Weekly digest: N project(s) with open items".

If you set a custom message on the rule, it replaces the default wording for every item that rule finds. Severity is Error, Warning or Info, and Error is the default. Severity only changes the icon shown in front of each item. It does not change who receives the message, how fast, or whether the item appears in the digest. Messages are written in English.


The weekly digest and once-only reminders

The digest and the nightly check follow fixed schedules. You cannot change the time, but your rules switch them on and off, because they only run when a rule uses them.

  • Weekly digest. Every Monday at 09:00 in Europe/Stockholm time. It covers notification rules that use the "project is updated" or "inactive for N days" trigger, for open projects. It does not include status, stage or role notifications, and it never changes a project. Each recipient gets one message that lists their projects with open items, and nothing is sent when there is nothing to report. A manager can also run it on demand from chat. If a digest completed in the last 30 minutes, a second run is skipped.

  • Nightly check. Every night at 06:00 UTC for rules with the "inactive for N days" trigger. A reminder for a stale deal is sent once per project when the project first crosses the limit. It is sent again only after someone works on the project and it goes quiet again. A reminder that could not be delivered is retried on later nights. If two inactivity rules match the same project, only the first rule's reminder is sent.

  • Nightly limits. Each night's run handles at most 150 actions, notifications and project updates together, or 10 minutes of work. The rest is picked up the next night. A rule that changes a project acts once per project per night.

  • Real-time notifications. A rule with the "project is updated" trigger notifies on every matching update, with no once-only limit. A rule with no conditions on that trigger would notify on every save, so add a condition.


Why your team needs it

A pipeline is only as useful as it is accurate, and accuracy slips when keeping it clean depends on people remembering to check. Pipeline Assistant removes that dependency.

  • No manual pipeline reviews. Deals are checked automatically as they change, not in a weekly meeting.

  • Nothing slips. Missing information and stale deals surface on their own, before they cost you a sale.

  • Fixes are one click away. Every message links to the project in Cinode.

  • Alerts reach people where they work. Messages arrive in Slack or Microsoft Teams, not in another inbox.

  • Rules fit your process. You decide what "complete" means at each stage, and Pipeline Assistant enforces it.


Secure and private by design

Pipeline Assistant works through the Chat Agent and inherits its security model.

  • You are only ever you. When you act from chat, the Chat Agent identifies you from your verified Slack or Teams account, never from anything typed in a message.

  • Changing deals from chat is limited to managers. Moving a project, changing its status, undoing a stage move and running the digest on demand require a manager, which means the Company manager access level or higher. Subscribing yourself to alerts is open to any user. Note that a manager can change any project that Pipeline Assistant can reach. It is not limited to the manager's own teams or customers.

  • Notifications go to the right people. Messages go only to the recipients a rule names, matched by their Cinode email.

  • You control your own messages. Any person can ask the Chat Agent to pause or stop direct messages from Pipeline Assistant. Each kind of message, such as real-time alerts, the weekly digest and nightly reminders, is controlled separately. Posts to shared channels are not affected, and the administrator of the integration controls those.

For the full security model, see Meet the Chat Agent.


Set up Pipeline Assistant

Setup is self-service and happens in Cinode Flows. An administrator installs Pipeline Assistant and steps through its configuration wizard.

  1. Install from Cinode Flows. In Cinode, go to Flows > Integrations, find Pipeline Assistant and click Add. Installing needs the Admin and Flows permissions. See Cinode Flows.

  2. Connect Cinode. On the Connections page, authorise Cinode when the wizard asks.

  3. Set up the Chat Agent. Pipeline Assistant delivers through the Chat Agent, so it must be set up for the same workspace first. See Chat Agent: Admin setup. If it is not connected yet, the "Send notification" action is labelled unavailable, and the rules you save start working once it is.

  4. Define your rules. On the Rules page, build the when, if and then rules for your pipeline. You can add as many as you need and change them at any time. A fresh rule starts with the "project is updated" trigger. Before the Chat Agent is connected, a fresh rule also starts with the "Move to stage" action, which is not allowed with that trigger, so change one of them before you save.

The Connections page also has a setting called Process Self-Triggered Events, off by default. Leave it off in most cases. When it is on, Pipeline Assistant also reacts to changes that its own rules made, which can cause chains of automations. Pipeline Assistant already runs the follow-up rules described above, so you do not need it for that.

Pipeline Assistant starts working the next time a matching project changes. See Pipeline Assistant: Common Use Cases for ready-made rules.


Frequently asked questions

Where do the notifications appear?

Notifications appear in Slack or Microsoft Teams, delivered through the Chat Agent. Real-time messages go to the recipient set on the rule, and the weekly digest goes to each rule's recipient.

What if the Chat Agent is not set up?

Pipeline Assistant has no other way to deliver, so notifications are skipped until the Chat Agent is connected. Rules that move a project or change its status still work. See Pipeline Assistant: Troubleshooting.

Can I require several things at one stage?

Yes. Add several conditions to one rule, so all of them must match, or add several rules to the same stage. In real-time checks the items found are combined into a single message per recipient.

Can I turn off the weekly digest or the nightly checks?

Yes, by controlling your rules. The digest and the nightly check only run when you have rules that use them. There is no separate schedule to manage.

Why did I only get one alert about a stale deal?

Stale-deal reminders are sent once, when the project first crosses the limit. They are not repeated until someone works on the project. The weekly digest still recaps stale deals that have open items.

Who can move deals or change status from chat?

Only managers, meaning the Company manager access level or higher. Any user can subscribe or unsubscribe themselves to alerts.

Why was someone not notified?

People are matched to their chat account by email address. A person whose Cinode email does not match their Slack or Teams email, or who has no email in Cinode, is skipped. A person can also have asked the Chat Agent to stop direct messages from Pipeline Assistant. See Pipeline Assistant: Troubleshooting.

Can Pipeline Assistant mark a project Won when its roles are staffed?

Yes. Use a rule with the role trigger, the Roles staffed condition and the Set project status action. See Pipeline Assistant: Common Use Cases for the exact settings.

Did this answer your question?