Group unanswered pricing and support threads, then prepare reply drafts without sending them.
Starting request
“Every weekday at 15:00 [timezone], find unanswered pricing and support threads in Gmail, group them by topic, and prepare reply drafts. Do not send them; post the draft links in my Slack DM.”
Use this as a starting point, then replace the example details with the sources, scope, and destination your team uses.
The example gives you a useful structure. The connections, scope, and schedule should match the way your team actually works.
Connect Gmail. OpenTag can only use the accounts and records those connections allow.
Name the exact accounts, projects, owners, date range, and time zone that matter. Replace the example details with your team’s own.
Run it once, review the source links and Slack destination, then keep or adjust the every weekday timing.
Keep the same team context and find another recurring job to hand off.
Group open HubSpot tickets by age and theme and call out requests without an owner.
HubSpot
Slack“Every morning at 08:30 [timezone], group open HubSpot support tickets by age and theme, call out any without an owner, and post links to the oldest requests in #support.”
Batch new human messages from invited support channels and point out requests that still need a reply.
Slack“Every hour, batch the new messages from people in the invited support channels. Group them by theme and post any unanswered requests in #support-triage.”
Name what to read, the period to cover, the result you need, when it should run, and where it should go. Run it once and check the result before relying on the schedule.