Triage new Smartsheet intake requests and flag P1s in Slack
Every half hour, unscored requests in your intake sheet get a work type, priority, effort estimate and owning team, with urgent ones posted to Slack.
Every 30 minutes between 8am and 6pm on weekdays, triage the new intake requests piling up in my Smartsheet request sheet.
Start by pulling the request sheet with the Smartsheet Get Sheet operation, or use Search in Sheet, and find every row where the Triage Status column is still empty. Those are the untriaged requests. Skip any row that already has a triage status so nothing gets scored twice.
For each untriaged row, read the free-text request description and decide four things: the work type, a priority from P1 to P4, a rough effort estimate, and the right owning team. Use the request's stated deadline and its business impact as the main signals. A hard external deadline, blocked revenue, or a customer-facing outage pushes the priority up; a nice-to-have ask with no date and no stated impact sits near the bottom.
Write those judgements back into the row with Smartsheet Update Rows, filling the work type, priority, effort estimate and owning team columns, and setting Triage Status so the row is not picked up on the next run.
Then use Create Discussion on Row to leave a short comment, two or three sentences, explaining the reasoning behind the call and naming the deadline and impact signals it was based on. This comment is the audit trail: a human should be able to read it, see why the request was scored the way it was, and override the call if they disagree.
Anything scored P1 should also be posted to my operations Slack channel using the Slack Send a Message operation. Include the requester, a one-line summary of the ask, the deadline, the owning team and a link back to the row, so it gets picked up the same day rather than waiting for someone to notice it in the sheet.
If a request is too vague to score, do not guess. Set its Triage Status to "Needs Info" instead of assigning a priority, and leave a comment on the row saying exactly what is missing, for example the deadline, the business impact, or which system or customer it affects.
If there are no untriaged rows when the workflow runs, do nothing and finish quietly. Do not post to Slack when there is nothing new to report.
What does this prompt do?
- Checks your request sheet every 30 minutes during working hours and finds the rows that have not been triaged yet.
- Reads each free-text request description and assigns a work type, a priority from P1 to P4, a rough effort estimate and the owning team, judged mainly on the stated deadline and business impact.
- Fills the decision into the row and adds a short comment explaining the reasoning, so a human can audit or override any call. Requests that are too vague get marked Needs Info instead of a guessed score.
- Posts every P1 to your operations Slack channel so the urgent work gets picked up the same day.
What do I need to use this?
- A Smartsheet login with edit access to the sheet your requests land in
- An intake sheet with a free-text request description plus columns for triage status, work type, priority, effort and owning team
- A Slack workspace and the channel your operations team watches for urgent work
How can I customize it?
- Change the schedule: run it every 15 minutes, hourly, or only at the start and end of each day.
- Rename the priority scale, work types or team names so they match the dropdown options already on your sheet.
- Decide what gets escalated: send P2s to Slack as well, or point different owning teams at different channels.
FAQs
What happens to requests that are too vague to score?
Can I override a priority I disagree with?
Will the same request get triaged twice?
Why not just use Smartsheet's built-in automation?
Do the priority levels have to be P1 to P4?
Related templates
When your flight moves, your calendar times get corrected automatically and you get a Slack note naming the meetings you're about to miss.
Every 15 minutes, forwarded phishing reports get traced back to the server that really sent them, with a verdict in Slack and the worst senders reported.
Every weekday at 7am, sign in to the tender portals you track, filter new notices against your bid criteria, and open a deal for the ones worth chasing.
Every Monday, rank the week's matches by expected demand, put the big ones on your venue calendar, and post a rota-ready summary to Slack.
Every Tuesday we pull your best new reviews, draft social captions, email testimonials and product page quotes, then stage them in Notion for approval.
Every weekday morning, unfulfilled orders get an address check: harmless typos fixed automatically, risky addresses held with a note to the customer.
Stop hand sorting your intake queue.
Set this up once and new requests arrive scored, assigned and explained before your team even opens the sheet.