Who it is forA sales manager reviewing a pipeline that an agent has been updating on its own schedule.
The problemAutomated changes to records are hard to trust when nobody can see how a conclusion was reached.
The outcomeThe manager can see each step, why leads were dropped, and answer any question the agent could not settle.
What you need first
- Bun and Docker installed
- A Google or Microsoft OAuth client, or your own identity provider set up later under Settings → SSO
- A value for BETTER_AUTH_SECRET and an ALLOWED_SIGN_IN domain or address
- Optional: a Context API key for company brand data and LinkedIn lookups, and a PERPLEXITY_API_KEY for web research
Steps
- Open a deal in the CRM and select the Agent tab
- Read the steps the agent took and the leads it threw away with reasons
- Answer any open question the agent asked about two people who might match
- Check that schedule_recheck entries show the reason the agent gave for returning
Prompt for your agent
In the trycompai/crm CRM, open the Agent tab for the deal <deal-name>, list each step, each discarded lead with its reason, and each open question. Report those items in a short table. Verify that every schedule_recheck entry includes a stated reason.
Caveat. The Agent tab only shows conversations after AGENT_BRIDGE_SECRET is set in both processes, and otherwise reports that it is not configured.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page