add_competitor
ChatGPTAdd a competitor to track. Ripplewatch will begin watching their pricing, hiring, product changes and press. If the domain looks dead or is a placeholder, it is not added and alternatives are returned; call again with force=true to add it anyway.
add_context_note
ChatGPTSave anything free-form the team knows that no CRM holds, so Ripplewatch can line it up against why deals are lost and what competitors are doing: what they are building and when it ships, a pricing or packaging change, a customer's offhand comment, a sales-call insight, something about the market. Pass the user's words as they said them, with the date if they gave one (effective_on). Unlike set_context it adds a note and never overwrites anything. The more of this, the sharper the answers. It is tagged automatically (what kind, which product areas, which loss themes, when it ships).
ask
ChatGPTAsk a free-form question about the competitors this account tracks, answered against the account's own positioning, ICP and the last 90 days of scored signals. Examples: 'Should we worry about Acme's new pricing?', 'What is our biggest exposure right now?'. Takes a few seconds and uses more compute than the read tools, so prefer get_briefing or get_competitor for simple lookups.
draft_cancellation_survey
ChatGPTUse when a consumer or subscription company sees churn but does not know why customers leave, or whether they also use a competitor. Returns this company's tracked competitors, who it sells to, its latest churn read, and the three-question structure for a short cancellation survey. Write the survey from it in the user's own tone: plain language, under 30 seconds, no discount pitch. Offer the tracked competitors as answers, always include I use both and I'm not switching, and say where to place it (the cancel screen or a follow-up email). Ripplewatch does not host or send the survey. When answers come back, count them by answer and log them with log_customer_feedback or, for individual customers, log_win_loss with outcome churned.
get_briefing
ChatGPTStart here. What changed across the competitors this account tracks and what it means: the latest weekly verdict, which competitors are heating up or cooling, the highest-relevance recent signals, and this account's own momentum. Also returns the single best next step to make future answers more specific.
get_churn_and_growth
ChatGPTWhat Ripplewatch knows about a company's churn and growth: the read of the monthly numbers it has (whether churn is rising, how fast customers are growing), whether churn started rising near a tracked competitor's pricing or product move, and how the churn rate sits against a published range for that kind of product, with its source. Use it when the user asks whether churn is a problem, why it might be rising, or how they compare to their industry. It shows timing, never cause: say how many months the read rests on and that a competitor move landing nearby is a lead, not proof. If there are no numbers yet, say so and offer log_customer_metrics.
get_competitor
ChatGPTEverything on one tracked competitor: momentum with the drivers behind the score, recent signals, and how many deals the account has logged against them.
get_deal_impact
ChatGPTThe answer to 'which competitor moves are actually costing us deals, and what should we do about it?'. Reads every logged deal by the REASON it was lost (most never name who won), lines the recurring reasons up against competitor pricing, product and hiring moves and their Momentum, and against the team's own notes (what they are building and when). Returns ranked findings with evidence, a confidence, and a next step, plus how much deal history there is and what more would unlock. Use it when the user asks why they are losing, what to build or say next, or whether a competitor's move matters. If there is little data it says so and says what to add.
get_momentum
ChatGPTMomentum (Heating up, Steady, Cooling, Gone quiet) for every tracked competitor, plus this account's own momentum built from its NPS trend and win-rate trend.
get_next_step
ChatGPTWhat single piece of information from the user would most improve future answers right now, and why. Call this when the user asks how to get more out of Ripplewatch, or when answers feel generic.
get_slack_setup_link
ChatGPTReturns the link to connect Slack for a weekly Momentum digest delivered to a channel, on top of asking here directly. The link requires being signed in to the Ripplewatch account in a browser — tell the user to open it there, not paste it back here.
get_trends
ChatGPTRecurring themes across the account's logged win/loss reasons and scored customer feedback, each linked to the competitor signal that helps explain it. Empty until enough reasons are logged.
how_to_use
ChatGPTCall this when the user asks how Ripplewatch works, how to get their win/loss data in, what momentum means, what notifications or emails they will get, how to see recent changes, what to ask, or how a team should use it. With no topic it returns the list of topics so you can offer them; with a topic it returns that explanation. Explain it conversationally in your own words, one topic at a time.
import_win_loss
ChatGPTBring in deal history in bulk. Use this when the user has a CRM, spreadsheet or other connected tool holding closed-won/closed-lost deals: read the rows there, then pass them here as raw text, one deal per line, header row first if there is one, exactly as you read them (do not summarize or rewrite). Ripplewatch classifies every row, ties tracked competitors to their reasons, and suggests competitors it isn't tracking yet. Ask the user before pulling their data, and only pass rows you actually read. Up to about 600 rows per call.
list_competitors
ChatGPTThe competitors this account currently tracks, with domain and category.
log_call_mentions
ChatGPTRecord times a tracked competitor came up on a sales call. Pass only short verbatim snippets the user has given you (a sentence or two) of where the competitor was mentioned, never full transcripts. If all you have is a summary, pass a one-sentence summary and say it is a summary. Mentions of competitors that aren't tracked are reported back, not guessed. Ask the user before logging, and never invent a quote or a mention. Repeats are ignored, so sending the same mention again is safe.
log_customer_feedback
ChatGPTRecord one piece of customer feedback: a feature request, complaint or comment, with an optional 0-10 NPS score. Detractor and promoter reasons feed the same theme detection as win/loss.
log_win_loss
ChatGPTRecord the outcome of one deal against a competitor, with the reason if known. This is the most valuable input: it lets Ripplewatch tie a competitor's moves to real deals. A competitor that isn't tracked yet is suggested for tracking instead of rejected.
set_context
ChatGPTReplace how the account positions itself and who it sells to. The text you send overwrites what was saved for that field, and the old text is not kept, so confirm with the user before changing it. Everything Ripplewatch scores is judged against this, so keep it to a sentence or two each. Only the fields provided are changed.
start_here
ChatGPTCall this first in a new conversation, or whenever the user seems new, asks what Ripplewatch can do, or asks what to do next. Returns this customer's company name, whether their first competitor check has finished, the best early findings, prompts tailored to their competitors, and the single most useful next step. Use it to guide them like a friendly onboarding partner.