rulebase-co

@rulebase-co source repo

150 skills
0 followers
1 repo stars
2 weeks ago last updated

▌
Cx Churn Signal · rulebase-co
Use to find cancellation, downgrade and switching intent in support conversations, and to be honest about how much of your churn support can actually see. Trigger for "which customers are at risk of leaving", "find cancellation intent", "customers asking how to export their data", "top reasons customers asked to close their account", competitor mentions, or building a churn early-warning signal from support data.

1 repo stars
▌
Rulebase Setup · rulebase-co bundle
Use to get access to Rulebase and connect an AI client to it — signing up, finding your data region, installing the Rulebase MCP server in Claude Code, Claude Desktop or Cursor, and creating an API key for the REST API. Trigger for "connect Claude to Rulebase", "install the Rulebase MCP", "set up the Rulebase connector", "create a Rulebase API key", "how do I sign up for Rulebase", "Rulebase returns 401", "no token provided", or when Rulebase tools are missing from a session.

1 repo stars
▌
Cx Nrr Attribution · rulebase-co
Use when support or CS is being asked to claim a share of net revenue retention, expansion or churn reduction, to work out what can honestly be attributed and what cannot. Trigger for "how much NRR can support claim", "prove support's revenue impact", "attribute retention to CS", support ROI for a board deck, or two teams claiming the same expansion.

1 repo stars
▌
Cx Revenue At Risk · rulebase-co
Use to quantify the revenue exposed by unresolved support failures, complaints and escalations without inflating the number. Trigger for "how much revenue is at risk", "what are these support failures costing us", "revenue behind our open escalations", building a business case for fixing a support problem, or a revenue-at-risk figure that looks too large to believe.

1 repo stars
▌
Cx Erasure Plan · rulebase-co bundle
Use to build a data-subject erasure plan for support conversations — GDPR right to erasure, CCPA deletion, right to be forgotten. Trigger for "delete this customer's data", DSR or SAR erasure request, GDPR deletion from our helpdesk, redacting personal data from tickets, or working out what can and cannot be erased.

1 repo stars
▌
Cx Expansion Signal · rulebase-co
Use to find upgrade, seat-growth and new-use-case signals that customers give support and nobody routes anywhere. Trigger for "find upsell opportunities in support", "customers hitting plan limits", "which accounts are asking about enterprise features", expansion signals from tickets, or support-sourced pipeline.

1 repo stars
▌
Cx AI Disclosure · rulebase-co
Use to design and audit how customers are told they are interacting with AI, or that AI was involved in a decision about them, and to evidence that it happened. Trigger for "do we tell customers it's a bot", "AI disclosure requirements", "should the bot say it's not human", "customer asked if they were talking to a person", AI transparency obligations, or evidencing that an AI-assisted decision was explained.

1 repo stars
▌
Cx Case Timeline · rulebase-co
Use to reconstruct what actually happened to one customer across every conversation, channel and handoff, for an escalation, complaint, post-mortem or goodwill decision. Trigger for "build a timeline for this customer", "what happened on this case", "summarize the back-and-forth before I decide", "when were they first told", escalation summaries, complaint investigations, or a case spanning several tickets.

1 repo stars
▌
Cx Wip Limits · rulebase-co
Use to set concurrency and work-in-progress limits for support teams — chat concurrency, personal WIP on async work, and limits as quality protection rather than arbitrary caps. Trigger for "how many chats per agent", "concurrency settings", "WIP limits", "agents juggling too many tickets", async backlog per person, or quality dropping as concurrent load rises.

1 repo stars
▌
Cx Complaints Sla · rulebase-co bundle
Use to compute and monitor regulated complaint deadlines — acknowledgement, holding response, final response — against business-day calendars, and to find cases about to breach. Trigger for "are we meeting our complaint deadlines", "complaint SLA breaches", "final response deadline", "which complaints are about to breach", complaint ageing reports, or building a complaints deadline monitor.

1 repo stars
▌
Cx Macro Audit · rulebase-co
Use to audit canned responses, macros, templates and saved replies for staleness, contradictions, overuse and gaps. Trigger for "audit our macros", "are our canned responses up to date", "which templates do agents actually use", macro sprawl, template cleanup, conflicting saved replies, or before migrating macros to a new helpdesk.

1 repo stars
▌
Cx Support Led Growth · rulebase-co
Use to find where support can drive adoption, referral and retention without turning into a sales channel, and to measure whether it worked. Trigger for "can support drive growth", "support-led growth programme", "should agents mention other features", advocacy and referral from support, adoption nudges in support conversations, or a support team being given a revenue target.

1 repo stars
▌
Rulebase Work Items · rulebase-co bundle
Use to push back-office work into Rulebase over the REST API so it can be evaluated like a conversation, with a dry-run plan, idempotent external ids and an audit log. Trigger for "send our back-office work to Rulebase", "push work items", "QA our operations team", "get case work into Rulebase", disputes or KYC queues with no customer on the line, or duplicate work items appearing after a re-run.

1 repo stars
▌
Cx Change Evidence · rulebase-co
Use to prove that a support process, policy or script change actually took effect — when, for whom, and whether behaviour followed — rather than that it was approved. Trigger for "prove we made that change", "when did this policy actually change", "did the team adopt the new process", evidencing remediation, "we told everyone" claims, or a change that was signed off and never landed.

1 repo stars
▌
Cx Control Testing · rulebase-co
Use to test whether a support control actually operates, the way an auditor would test it, rather than confirming it exists on paper. Trigger for "test our controls", "does this control actually work", second-line assurance over support, control effectiveness testing, preparing for an internal audit, or a control that passed review and then failed in practice.

1 repo stars
▌
Cx Dispute Quality · rulebase-co
Use to audit how payment disputes, chargebacks and unrecognised-transaction claims are handled against scheme deadlines and evidence standards. Trigger for "audit our dispute handling", "chargeback quality review", "are we meeting scheme deadlines", unrecognised transaction claims, provisional credit decisions, or a customer complaining their dispute was rejected unfairly.

1 repo stars
▌
Cx Effort Score · rulebase-co
Use to measure customer effort from behavioural signals instead of CES surveys, and to audit whether a composite effort score is honest. Trigger for "customer effort score", "behavioural CES", effort without survey, repeat contacts and channel switches, transfers and reopens, or "our CES doesn't match operational data".

1 repo stars
▌
Cx Queue Design · rulebase-co
Use to design support queues and the skill taxonomy routing rules depend on — not as an org chart mirror, but as staffable combinations of skill, priority and channel. Trigger for "how should we structure our queues", "too many queues", "queue design", "routing taxonomy", "catch-all queue growing", overflow rules, or redesigning queue structure before changing routing rules.

1 repo stars
▌
Cx Voice QA · rulebase-co
Use to set up or fix quality assurance for voice/phone support, including transcript-based and AI-graded call QA. Trigger for "QA our calls", "score phone conversations", call transcription accuracy for QA, diarisation or speaker attribution problems, word error rate, grading calls from transcripts, or adapting a chat/email QA scorecard to voice.

1 repo stars
▌
Cx Onboarding Friction · rulebase-co
Use to find the activation blockers visible in support contacts from new customers, before they show up in retention numbers months later. Trigger for "why aren't new customers activating", "what do new customers contact us about", onboarding drop-off, time-to-value analysis, first-90-days support experience, or a retention problem that traces back to activation.

1 repo stars
▌
Cx Renewal Risk Review · rulebase-co
Use to build an account's cumulative support record ahead of a renewal or QBR, so the review reflects the whole relationship rather than the most recent ticket. Trigger for "prepare for this renewal", "what has this account's support experience been", "which accounts are at risk before renewal", QBR preparation, account health review, or an account that renewed badly with no warning.

1 repo stars
▌
Cx Data Flow Review · rulebase-co
Use to map where support conversation data actually goes — systems, vendors, countries, AI providers — and compare it against what the privacy notice and records say. Trigger for "where does our support data go", "map our data flows", "which vendors process our conversations", cross-border transfer review, ROPA accuracy for support, or a new tool that was connected without a review.

1 repo stars
▌
Cx Disclosure Audit · rulebase-co
Use to check that required disclosures, consents and notices were actually given in support conversations — the right wording, at the right point, through a channel the customer could act on. Trigger for "did we give the required disclosure", "are we capturing consent properly", "recording notification audit", "check our mandatory notices", disclosure compliance, or a complaint that a customer was not told something.

1 repo stars
▌
Cx Third Party Risk · rulebase-co
Use to review how an outsourcer, BPO or vendor handles your customer data and meets your conduct obligations, using evidence from the work rather than from their questionnaire answers. Trigger for "review our BPO's data handling", "vendor risk assessment for our outsourcer", "are our partners compliant", third-party oversight, outsourcing due diligence, or a supplier audit of a support vendor.

1 repo stars
▌
Cx Cost To Serve · rulebase-co
Use to build a defensible cost per contact and cost to serve by driver, channel or customer segment, for automation business cases and budget decisions. Trigger for "what does a ticket cost us", "cost per contact", "what would automating this save", "cost to serve by segment", building a business case for a bot or a process change, or a savings claim that looks too good.

1 repo stars
▌
Cx Routing Audit · rulebase-co
Use to find where support routing is failing — misrouted contacts, reassignment chains, unassigned work, and queues nobody owns. Trigger for "why do tickets bounce between teams", "are we routing correctly", "tickets sitting unassigned", "how many tickets get reassigned", ticket ping-pong, or reviewing routing rules and queue design.

1 repo stars
▌
Cx Survey Design · rulebase-co bundle
Use to design or fix a customer support survey — CSAT, NPS, or CES — and to diagnose response bias. Trigger for "design a CSAT survey", "our CSAT doesn't match reality", "should we use NPS", survey response rate, non-response bias, survey timing or scale choice, comparing satisfaction across teams or channels, or interpreting a satisfaction trend.

1 repo stars
▌
Cx Team Topology · rulebase-co
Use to decide how to split a growing support organisation — by product, segment, channel, or complexity — and when pods beat shared queues, accounting for coordination cost. Trigger for "team topology", "how should we split the team", "organise support by product or queue", "when to create pods", "support team structure", growing headcount, or coordination overhead between sites.

1 repo stars
▌
Cx Cost Of Poor Quality · rulebase-co
Use to quantify what support quality failures cost — rework, credits, escalation handling, complaints and churn — with the causal limits stated. Trigger for "what do our quality failures cost", "cost of rework in support", "business case for improving quality", "how much is bad support costing us", or a quality investment that needs a number attached.

1 repo stars
▌
Rulebase Upload Calls · rulebase-co bundle
Use to push call recordings into Rulebase over the REST API when the phone system has no native connection, in reviewed batches with a dry-run plan, resume and audit log. Trigger for "upload calls to Rulebase", "import call recordings", "backfill our call history into Rulebase", "get XCally calls into Rulebase", "Rulebase isn't seeing our calls", or bulk-ingesting audio for QA evaluation.

1 repo stars
▌
Cx Backlog Triage · rulebase-co
Use to analyse a support backlog and find the conversations actually at risk — never-touched tickets, work stalled on your side, customers stranded with a bot, and unassigned open work. Trigger for "report on our open tickets", "daily outstanding tickets report", "how many tickets have we not responded to", "find tickets waiting on us", "customers stuck with a bot and no human", aging backlog, or a backlog that keeps growing.

1 repo stars
▌
Cx Career Pathing · rulebase-co
Use to design support career progression with IC and lead tracks, skill gates instead of tenure alone, and paths that do not treat leaving the phones as the only promotion. Trigger for "career pathing", "progression framework for support", "IC track", "how do agents get promoted", "support ladder", "team lead vs senior agent", or fixing promotion bottlenecks and title inflation.

1 repo stars
▌
Cx Hiring Profile · rulebase-co
Use to define what actually predicts support performance in your organisation and build a hiring profile around validated predictors — structured work samples, not vibes. Trigger for "hiring profile", "what should we look for in support hires", "interview scorecard for agents", "reduce bad hires", "work sample test", screening criteria review, or checking whether your interview process predicts ramp and QA.

1 repo stars
▌
Cx Incident Comms · rulebase-co
Use to run customer support communications during an outage or major incident — banners, macros, status page, volume planning, and postmortem inputs. Trigger for "incident comms playbook", "support during outage", status page and help centre banner, macro for widespread issue, staffing surge, or freeze non-incident work.

1 repo stars
▌
Cx Customer Health Score · rulebase-co
Use to design or audit the support contribution to a customer health score, so the score predicts something instead of averaging weakly-related signals into a colour. Trigger for "build a customer health score", "add support signal to health scoring", "our health scores don't predict churn", red/amber/green account scoring, or a health score nobody trusts.

1 repo stars
▌
Cx Win Loss From Support · rulebase-co
Use to extract competitor mentions, switching language and feature-gap evidence from support conversations as an input to win/loss and product strategy. Trigger for "what competitors do customers mention", "why do customers switch away", "find feature gaps customers ask about", competitive intelligence from support, or win/loss analysis that only samples deals sales remembers.

1 repo stars
▌
Rulebase Workspace SQL · rulebase-co
Use when querying a Rulebase workspace with SQL through the MCP server's query tool — writing queries that finish inside the statement timeout, and avoiding the join fan-outs that silently inflate QA evaluation counts. Trigger for "query my Rulebase data", "the query timed out", "statement timeout", "canceling statement due to statement timeout", counts that don't reconcile between two Rulebase queries, criterion counts exceeding team counts, or any multi-step analysis over Rulebase conversations and evaluations.

1 repo stars
▌
Cx Emerging Harm Scan · rulebase-co
Use to scan support conversations for a harm nobody has categorised yet — a new failure mode, a scam pattern, or a product change hurting a group of customers before it shows in any metric. Trigger for "is anything new going wrong", "scan for emerging issues", "early warning from support", horizon scanning, a new scam pattern, or preparing for a question about what you might be missing.

1 repo stars
▌
Cx Flow Efficiency · rulebase-co
Use to analyse touch time vs elapsed time across the resolution path — queue wait, customer wait, back-office wait, and where elapsed time hides real delay. Trigger for "flow efficiency", "touch time vs elapsed time", "where is the time going", "customers waiting on us", back-office bottlenecks, idle time in cases, or end-to-end time much longer than handle time.

1 repo stars
▌
Cx Journey Mapping · rulebase-co
Use to map support contacts onto the product lifecycle, interpret contact as a lifecycle signal, and avoid journey-map theatre. Trigger for "customer journey map support", "contact by lifecycle stage", onboarding support drivers, churn and support overlap, stage-specific contact reasons, or when journey mapping is worth doing.

1 repo stars
▌
Cx Onboarding Ramp · rulebase-co
Use to measure how long new support agents take to reach proficiency and where their ramp stalls, so training and nesting can be targeted. Trigger for "how long until new hires are productive", "time to proficiency", "how is the new cohort doing", nesting or ramp design, comparing training cohorts, or a new hire being assessed before they have had time to ramp.

1 repo stars
▌
Cx Service Tiering · rulebase-co
Use to design VIP or tiered support programmes and to test whether higher tiers actually deliver better outcomes. Trigger for "VIP support programme", "service tiering", queue priority for premium customers, entitlement vs priority, tier inflation, or "does our enterprise tier get faster support".

1 repo stars
▌
Cx Collections Conduct · rulebase-co
Use to audit arrears, collections and financial-difficulty conversations for fair treatment — forbearance offered, pressure absent, vulnerability recognised. Trigger for "audit our collections calls", "are we treating customers in arrears fairly", "did we offer forbearance", financial difficulty handling, payment plan conversations, or a complaint about collections conduct.

1 repo stars
▌
Cx Duplicate Detection · rulebase-co bundle
Use to find duplicate or repeated support conversations and produce a reviewable merge plan. Trigger for "find duplicate tickets", "customers contacting us twice about the same thing", deduplicating a helpdesk, cleaning up ticket volume, or measuring how much of your contact volume is the same issue submitted more than once.

1 repo stars
▌
Cx Pii Redaction Audit · rulebase-co
Use to check whether a conversation export, dataset or AI pipeline is leaking personal data that should have been redacted, and to measure how well the redaction actually works. Trigger for "is this export safe to share", "check our redaction", "can we use support transcripts for training", sending transcripts to a vendor or model, "is there PII in this dataset", or before opening support data to a wider audience.

1 repo stars
▌
Cx Quality Attestation · rulebase-co
Use to sign off a QA period for audit or governance — stating what is being attested to, on what evidence, and with which limitations. Trigger for "sign off the QA period", "attest to our quality results", "monthly QA governance pack", "certify the quality figures", or being asked to confirm quality was assured for a period.

1 repo stars
▌
Cx Redress Consistency · rulebase-co
Use to audit whether similar customers with similar failures received similar redress, and to find variation that could not be defended. Trigger for "are our refunds consistent", "do we compensate similar cases the same way", "audit our goodwill decisions", redress fairness review, customers who escalate getting more, or a complaint that someone else was treated better.

1 repo stars
▌
Cx Channel Strategy · rulebase-co
Use to decide which support channels to offer, add, or retire, and to audit channel mix against accessibility obligations and cost to serve. Trigger for "should we add chat", "which channels should we offer", channel strategy, cost to serve by channel, accessibility requirements for support, opening a new contact route, or retiring phone or email.

1 repo stars
▌
Cx Dashboard Review · rulebase-co
Use to audit a CX dashboard for tiles nobody acts on and metrics nobody agrees on — assign an owner per tile, apply kill criteria, and run an actionability test before adding or keeping a chart. Trigger for "clean up the dashboard", "too many metrics", "which KPIs should we keep", dashboard audit, metrics review workshop, "nobody looks at this anymore", or before a BI migration or exec-pack refresh.

1 repo stars
▌
Cx Incentive Design · rulebase-co
Use to design support incentives that improve behaviour without destroying the metric — pairing pay with guardrails, naming gaming modes, and choosing measures that survive Goodhart pressure. Trigger for "incentive plan", "agent bonus scheme", "SPIFF design", "pay for QA score", "what metric should we bonus", CSAT incentives, or reviewing whether a comp change is driving gaming.

1 repo stars

150 published skills · page 2 of 2