Sales
Sales pipeline alerts that complement your CRM dashboard
Use sales alerts to flag stale opportunities and pipeline gaps. Keep your CRM and sales dashboard, and monitor exported data with Kisu.
Make stale pipeline a review prompt
Illustration · scheduled checks every 12 or 24 hours
- ProposalNorthstar renewal18 days since activityReview the next follow-up.
- NegotiationAcme expansion21 days since activityConfirm the next step.
- DiscoveryHarbor pilotNo activity dateCheck the source record.
Example Slack notificationReview next steps in your CRMA matching check queues a notification. This is not an exact message preview.A sales dashboard shows pipeline health when someone opens it. Sales alerts help a team notice an exception between reviews. Keep your CRM as the system of record. Use Kisu to check selected sales pipeline data that your existing process puts in BigQuery or Google Sheets.
Start with three sales pipeline questions
- Are open opportunities going stale? Count open deals with no recorded activity for a period that fits your sales cycle. Ask owners to confirm a next step.
- Is near-term pipeline too small? Sum open opportunity value expected to close in the target period. Compare it with a documented coverage floor.
- Is new qualified pipeline slowing? Sum newly qualified opportunity value over a rolling window. Review demand generation and qualification together.
These are review prompts, not automatic diagnoses. An inactive record may reflect missing CRM logging. A low pipeline total may reflect a delayed export. Give each alert an owner who can check both the business issue and the data.
Example: flag stale opportunities in BigQuery
This example asks whether at least one open opportunity has had no recorded activity for 14 days. It also flags open opportunities with no activity timestamp. Replace the schema and definition of “open” with your own.
SELECT COUNT(*) > 0 AS needs_attention
FROM `your-project.crm.opportunities`
WHERE is_open = TRUE
AND (
last_activity_at IS NULL
OR last_activity_at < TIMESTAMP_SUB(
CURRENT_TIMESTAMP(), INTERVAL 14 DAY
)
)The query returns a Boolean, not a deal list. Kisu is not a CRM task manager and does not update opportunity records. Use the matching notification to open your CRM or dashboard and inspect the relevant deals. Google bills BigQuery usage separately.
Use a spreadsheet when the pipeline is small
For a Google Sheets workflow, prepare a tab containing only open opportunities. Add a numeric Days since last activity helper column. A Maximum greater than 14 condition can flag at least one stale numeric value.
Handle missing activity dates explicitly in the sheet. Blank and text cells are ignored by Kisu, so a blank helper value will not trigger a numeric threshold. If missing dates require a review, give them a deliberate numeric flag in a separate helper column.
Do not rely on a sheet filter to exclude closed deals. Hidden and filtered rows are still included. Use a dedicated tab or helper column that represents the intended subset.
Add Kisu without replacing your pipeline CRM
- Use your existing export or data pipeline to put CRM data in BigQuery or Sheets. Kisu does not supply a direct CRM connector.
- Confirm refresh timing, deduplication, and the meaning of your stage and activity fields.
- Connect the source in Kisu and configure the condition. Test a BigQuery query before saving.
- Select a tested Slack destination and choose checks every 12 or 24 hours.
- Review History for check results and delivery status. Use the CRM to assign and complete follow-up.
Match the alert cadence to the sales process
A daily pipeline review can fit a scheduled check. An instant inbound-lead response needs a different workflow. Kisu is not a real-time sales routing tool.
Every successful matching check queues a notification. If one stale deal keeps the condition true, the team will receive repeated messages. Start with one shared rule rather than many overlapping alerts. For a broader revenue review, use pipeline coverage and forecasting checks alongside it.
