
Tottenham cut 35 systems to one, and identity was the hard part
Tottenham Hotspur consolidated about 35 fan-facing systems onto Salesforce. The harder work is the one Rob Pickering names in passing: identity across touch points.
Topic coverage
Source-linked reporting and practical patterns organized around a shared enterprise applications question.

Tottenham Hotspur consolidated about 35 fan-facing systems onto Salesforce. The harder work is the one Rob Pickering names in passing: identity across touch points.

Salesforce claims three times fewer errors on CRM actions for Koa. That figure comes from Salesforce's own CRM benchmark, not an independent one.

Automatic capture ends the old CRM bargain. Recorded volume rises, the average record matters less, and the reason behind a decision becomes the scarce thing.

An employee who fails at self-service tries again tomorrow. A customer may just leave, and may hold a contract saying you owe them an answer.

A human reads around a bad knowledge article. An agent answers from it, which turns knowledge quality into an accuracy problem with a blast radius.

A customer portal collects a page from every team that asks. Decide who owns the scope, where the logic lives and what anonymous visitors see.

Oracle CX rarely leads a CRM shortlist, and the honest case for it sits at the quote-to-cash boundary rather than anywhere a demo can reach.

Record types or separate objects, contacts who exist nowhere, entitlements you may not need. The Case model choices that fix what you can report on for years.

Deflection metrics count three different outcomes as one success, and automation takes the cheapest cases first. Here is how to measure what you really saved.

Research, activity logging and quote assembly really do shrink. The judgment calls do not, and checking the agent's output before a customer sees it is new work.

Companies replace their CRM every seven to ten years, and the way they decided to represent a customer survives every one of those migrations.

Serving external customers from the ServiceNow incident table holds up until an outage, when the internal clock and the contract clock stop agreeing.

A decision framework for splitting a Salesforce org, and an honest look at what the split really costs once you're running two systems instead of one.

Routing rules pile up one exception at a time until nobody can explain why a lead landed where it did. Here is how to find the rule that actually ran.

Sales and service can keep their own screens. They have to share the customer identifier, the lifecycle states, the conflict rule, and the correction path.

A blank escalation reason usually marks a case that skipped its normal owner. Name what the blank means and route it before you make the field required.

Decide what moves before you touch a mapping rule, read the merge output yourself, and verify against totals the business already argues about.

Model queues on kinds of work, pin down the order your assignment rules evaluate in, and give every request that matches nothing a queue someone opens daily.

Capacity, priority and presence decide how Omni-Channel behaves at peak. Set them from real numbers, then test with two agents and one saturated queue.

An account hierarchy records a commercial relationship. Case visibility is a separate decision, and the hierarchy setting is the one that leaks a child's cases.

Agentforce agents are handed a job rather than a script, bounded by topics and instructions, and they see exactly what the user they run as can see.

A working method for auditing Salesforce profiles and permission sets, and removing the access you find without breaking someone's Monday.