Video Emotion Analysis for Customer Service (2026 Guide)

Updated October 2026: CX vendor map rebuilt after the Verint–Calabrio merger and Hume’s EVI API sunset (13 November 2026); EU AI Act Article 50(3) notice duty and California AB 1883 added.

Why Fora Soft wrote this emotion analysis playbook

We’ve been building video and AI products since 2005: 250+ projects across 20+ years, with a 50-person in-house engineering team. Emotion analysis keeps landing on our desk from telehealth, contact centres, market research and training-simulator clients, and we’ve shipped the transcript, voice and computer-vision layers it depends on; the vision side is the daily work of our computer vision development team. We’ve also talked clients out of emotion-recognition projects when the EU AI Act, Illinois BIPA or plain accuracy reality made them a bad idea.

This is the buyer-and-builder guide. We cover what the technology actually is, what works in customer service in 2026, the platforms shipping in production, the regulatory line you cannot cross, the cost model, and the build-vs-buy call. It ends with a five-question framework so you can decide fast whether to ship this feature, defer it, or never ship it. If you want the sibling reads: our guide to AI emotion detection in video conferences and our teardown of real-time emotion recognition software go deeper on adjacent problems.

One example we lean on: for VocalViews, a market-research video platform with 1M+ participants and clients like Samsung, Google and Netflix, we built the video-interview stack — recording, speech-to-text in 30+ languages, live translation and automatic transcription. That’s the same capture-and-transcript spine emotion analysis rides on. You can browse the rest in our project portfolio.

What video emotion analysis actually is

Video emotion analysis is the real-time reading of a customer’s emotional state from a video stream — their face, their voice, and sometimes their words. The output takes one of two shapes: discrete emotion labels (Ekman’s six basics: happy, sad, angry, surprised, disgusted and afraid, plus a neutral class and sometimes contempt) or dimensional scores on valence (positive to negative) and arousal (calm to excited).

In production it runs as a multimodal pipeline. Faces are coded with FACS (Facial Action Coding System) action units and a CNN or vision-transformer classifier. Voice is parsed for prosody: pitch, intensity, jitter, speech rate. Text is sentiment-classified with BERT/RoBERTa-class models. The three streams are fused either late (averaged scores) or with a cross-modal transformer; the face channel alone has five model families, compared in our guide to machine learning techniques and tools for video emotion recognition. Trimodal fusion is now the default in the research, and it buys 10–20 points of accuracy over any single channel. Here’s the catch worth remembering: even the best face model reads a fraction of real affect, so the fusion step is doing more work than the demo suggests.

Figure 1. One live call becomes three modality signals — face, voice and text — fused into a single customer-experience cue.

The accuracy reality — lab numbers vs production

Vendor demos quote 90%+ accuracy. Real call data tells a different story, and the pattern is consistent across 2024–2026 academic surveys: subtract roughly 15–25 points from any lab benchmark to estimate production accuracy on real customer audio and video. The gap comes from lighting, accents, cross-talk, cameras pointed at ceilings, and the simple fact that people mask what they feel on a support call.

Figure 2. Lab benchmarks vs realistic production accuracy. Every bar is anchored at zero; the light cap is the demo number you should discount.

Per-emotion accuracy is even more uneven. “Happy” detection on real calls runs above 90%; “fear” sits below 40%; the angry/frustrated split that matters most for customer service lands at 60–75% in good conditions and worse with low-light cameras, accented English or non-Western communication norms. It’s also worth knowing the science is contested: Lisa Feldman Barrett’s 2019 review argues you cannot reliably read a person’s emotional state from their face alone, which is exactly why voice and text carry so much weight in a serious build.

What this means for product: emotion analysis is a triage signal, not a verdict. Read the output as “this call may need a supervisor” rather than “the customer is angry.” Pair every alert with text context — the caller actually said “frustrated,” “cancel,” or “manager” — and the false-positive rate drops from 5–10% into the 1–2% band that agents will trust. Getting the accuracy target right is a non-functional requirement in its own right; we wrote a whole primer on non-functional requirements for exactly this reason.

The EU AI Act emotion-recognition ban you cannot cross

Most articles on this topic skip the part that can actually fine you. As of 2 February 2025, Article 5(1)(f) of the EU AI Act prohibits AI systems that infer the emotions of a person in workplace and education settings, except for medical or safety reasons (driver-fatigue detection is the textbook exception). The penalty for a prohibited practice reaches €35 million or 7% of global annual turnover, whichever is larger, and the penalty regime became enforceable on 2 August 2025.

What it covers. Inferring emotion from biometric data (facial images, voice, gait, physiological signals) for staff or learners. Agent-monitoring via webcam emotion analysis falls squarely inside the ban. So does student attention tracking and recruitment screening based on facial expressions. And here’s the part teams miss: consent does not cure it. In an employment context the practice is banned outright, so a “we asked the agent to opt in” clause is void. The Future of Privacy Forum’s analysis reads the line the same strict way.

What it does not cover. Inferring emotion of customers outside an employment or education context — with consent and a clear lawful basis — stays permissible, subject to GDPR Article 9 (special-category biometric data) and member-state law. Telehealth diagnosis, voice-of-customer analytics with consent, and safety fatigue detection sit outside the prohibition. The ban is also extraterritorial: if your system’s output touches people in the EU, it applies regardless of where you’re headquartered.

What changed in 2026. Since 2 August 2026, Article 50(3) of the AI Act obliges anyone deploying an emotion recognition system to inform the people exposed to it; the Commission’s final transparency guidelines of 20 July 2026 leave the format open but expect the notice no later than the first interaction. The Digital Omnibus, Regulation (EU) 2026/1744, pushed high-risk Annex III duties to 2 December 2027 but left the Article 5 ban untouched. In the US, California’s AB 1883, signed on 30 September 2026 and in force from 1 January 2027, bars employers from using AI surveillance tools to infer workers’ emotions, so agent-side emotion scoring now has a US red line too. The full legal map lives in our emotion detection guide to accuracy, law and cost.

Practical effect on CX. European contact centres analysing the agent’s face or voice for “tone coaching” can no longer ship that feature. Systems analysing the customer’s emotion still can — with consent, lawful basis, transparency and documented data minimisation. Most enterprise teams have responded by limiting inference to the customer side and by leading with voice prosody (which carries less biometric weight than face).

Figure 3. A compliance-first path: analyse staff in the EU and you’re banned; analyse consenting customers and the build opens up.

Customer service use cases that deliver ROI in 2026

1. Supervisor-assist on customer-side signal. Detect the customer’s emotion (face + voice) and raise a “may need a senior agent” flag to the supervisor. Inside the EU this is the safe pattern: the system never touches the agent. Verint bought Cogito in October 2024 for $38.2M and folded its real-time engine, which reads 200+ acoustic and linguistic signals, into a bot that scores live conversations. Inside the EU, configure that class of tool to score the customer, never the agent.

2. Post-call quality analytics. Aggregate customer-emotion trajectories across thousands of calls to find the words, products and processes that consistently turn customers angry. It’s post-hoc, anonymised and statistical — the lowest-risk regulatory profile you can pick.

3. Churn and CSAT prediction. In the projects we have seen, negative valence at the end of a call is one of the earliest churn signals you can get; validate it against your own churn data before you act on it. Route those calls to a retention queue and you convert a lagging metric into a live one. This is the same “measure what predicts revenue” logic we argue in our piece on why active users matter as a revenue metric.

4. Telehealth patient-state monitoring. Inside a doctor’s consent flow, emotion analysis flags pain, anxiety or depression markers a clinician might miss in a rushed tele-visit. The AI Act’s medical exception applies; HIPAA and GDPR Article 9 still apply in full.

5. Voice-bot escalation and sales coaching (US). AI voice agents can hand off to a human the moment frustration spikes — we cover that handoff in our AI call-assistant buyer’s guide, and our AI call agent development team wires that frustration-triggered warm transfer into custom phone agents. US-based sales orgs and training simulators (where the “agent” is a learner, not staff) sit outside the EU prohibition entirely.

Emotion analysis use cases that backfire

Replacing human empathy. Systems that detect frustration and auto-fire a generic “I understand you’re upset” line tend to see CSAT fall, not rise. Customers can tell when they’re being handled by a script.

Hiring decisions from candidate emotion. Banned in the EU, BIPA-exposed in Illinois, scientifically thin everywhere. Vendors still selling this in 2026 are walking a regulatory minefield.

Insurance “deception” detection. Microexpression-based lie detection has been debunked since the early 2020s, and there are already lawsuits in flight over it. Don’t ship it.

Retail in-store emotion tracking. Stack California biometric rules, New York facial-recognition disclosure, GDPR and the AI Act, and the 2024–2026 case-law trend is consistent: don’t do it without a meticulously reviewed legal basis.

Student attention tracking. Banned in the EU for education institutions. In the US, FERPA plus a long line of bad press around remote-proctoring tools makes it a poor bet.

The 2026 emotion analysis vendor map

Short answer: for a contact centre in 2026, the realistic choice is a CX suite that already scores voice and text — Verint, NiCE, Observe.AI, Uniphore or Invoca — with a face channel added only for consented video sessions. Standalone emotion APIs are shrinking: Hume, the best-known one, is shutting its developer APIs this year.

Two gaps to plan around. Microsoft retired explicit Azure Face emotion recognition in 2022 on responsible-AI grounds. Google Cloud Vision returns only four coarse likelihoods per face (joy, sorrow, anger, surprise), and AWS Rekognition returns eight emotion labels with a confidence score while warning that they are not a determination of a person’s internal emotional state — useful framing to copy into your own consent screen. For the face-model side, see our video emotion recognition tools compared.

Reference architecture for real-time emotion analysis

A real-time supervisor-assist deployment breaks into five stages. If you build on our AI-for-video-engineering track, the same shape shows up in most projects.

1. Capture. WebRTC for browser softphones (300–500 ms baseline latency, native to modern stacks); RTSP for legacy CCaaS or recorded-call playback. Hybrid is common — WebRTC live, RTSP for archived QA passes.

2. Pre-processing. Voice-activity detection, speaker diarisation, face detection (MediaPipe or YOLO) and face crops at 30 fps. Drop frames with no visible face to save GPU time. The transcript layer here is the same speech-to-text we compare in our speech-recognition round-up.

3. Inference cluster. Server-side and multimodal: facial CNN/ViT (30–50 ms), voice prosody (50–100 ms), text sentiment (20–40 ms), late fusion (10–20 ms). Total p95 latency lands near 200–300 ms with GPU acceleration. An NVIDIA T4 or RTX 4000 serves 10–30 concurrent calls; an A100 serves 200+.

4. Edge alternative. NVIDIA Jetson on-prem, a MorphCast-style browser SDK or an on-device Core ML face model. Sub-100 ms latency, near-zero cloud egress and a far better privacy posture for regulated workloads. The same voice-biometric handling we cover in our voice cloning and synthesis guide applies here.

5. Action layer. A sub-500 ms nudge to the supervisor UI (or, outside the EU, the agent), plus aggregated post-call analytics into the QA dashboard. This is where 90% of the product value lives — under-invest here and the rest of the pipeline is wasted compute.

Cost model — what emotion analysis really costs in 2026

SaaS pricing per analysed call runs $0.05–$0.30 depending on modality and volume. These are our working estimates as of October 2026: most CX vendors quote per seat or per minute and do not publish list prices. Voice-only prosody lands at $0.08–$0.15; video-plus-voice multimodal lands at $0.20–$0.30. Volume discounts bite fast: a 50M-call/year contract can reach $0.05/call, while a 5M-call/year deal sits around $0.15.

Worked build-vs-buy math. Take 5M analysed calls a year. At a blended $0.12/call, SaaS costs 5,000,000 × $0.12 = $600K/year. A custom build lands near $500K in year one (a GPU cluster plus delivery) and roughly $0.02/call in marginal ops, so 5M × $0.02 + $500K = $600K — the lines cross at about 5M calls. Below that, SaaS wins on every axis except IP ownership; above it, the build pulls ahead and keeps pulling. Because we deliver with Agent Engineering, our build number is usually below the integrator norm, which nudges the crossover left.

Figure 4. SaaS scales linearly with volume; a custom build front-loads cost then flattens. The crossover sits near 5M calls a year.

Hidden costs to budget. Compliance review and a data-protection impact assessment run $20–$60K. Domain-specific tone training runs $30–$100K. Each non-English language beyond the first runs $20–$50K. And false positives have an operational price: 30–60 seconds lost per wrong “angry” alert, times a 5–10% false-positive rate, across a 100-seat floor, is $5–$20K/month of drag if you never calibrate.

Mini case — one build we declined, one we shipped

The one we declined. An EU-based contact-centre client wanted real-time agent emotion analysis to “improve empathy” with face-and-voice nudges on the agent. Once we mapped the workflow against Article 5(1)(f), we said no — the deployment would have been unlawful, and consent wouldn’t save it. Instead we re-scoped to a customer-side system that flags supervisor attention with consent, a documented DPIA and a named lawful basis under GDPR Article 9. The client kept the value and stayed clear of a €35M-class fine. Want that same regulator check on your idea? Book a 30-minute call.

The one we shipped. Healthcare is where the customer-side pattern earns its keep. We build HIPAA-grade telehealth — CirrusMED, a subscription telehealth platform now licensed across 48+ US states, is one of ours — so an emotion-aware triage layer sits naturally on top: voice-prosody plus text sentiment on inbound calls, routing anxiety and pain markers to a nurse queue, on a HIPAA-eligible cloud with an on-prem option for the regulated tenant. Sub-300 ms latency, human-in-the-loop by design, and no facial biometrics stored beyond the session. We report accuracy on the client’s own calls before wiring any alert to a screen, because the lab number is never the number that matters.

Decision framework — ship emotion analysis in five questions

Q1. Are you in the EU and analysing employees or learners? If yes, stop. Article 5(1)(f) applies. Re-scope to customer-side analysis with full consent, or pick another feature.

Q2. What’s the lawful basis under GDPR, BIPA or CPRA? Consent is the cleanest. Legitimate interest rarely holds for biometrics. If you can’t name the basis in one sentence, you’re not ready to build.

Q3. Voice-only or full multimodal? Voice prosody carries less biometric weight, lower compliance friction and lower cost. Start there. Add facial only when the ROI case is clear and the consent flow is solid.

Q4. SaaS or custom? Under 5M calls/year, English-dominant, no on-prem — SaaS. Past 5M, regulated, multilingual, on-prem, or you’re selling emotion analysis as a feature — custom.

Q5. What’s the cost of the wrong answer? If the system misses an angry customer and an escalation goes unmanaged, what’s the loss? If it mis-flags a calm customer and the agent over-engages, what’s the productivity hit? Calibrate thresholds against the cheaper of the two errors, not against the demo.

Five pitfalls in almost every emotion analysis rollout

1. Believing the lab benchmarks. 95% on FER2013 becomes 70% on real calls. Re-test on your own audio and video before you commit budget or wire up alerts.

2. Treating the signal as a verdict. Pair every emotion alert with a text-keyword check (“cancel,” “refund,” “manager”) to drop the false-positive rate from 5–10% to under 2%.

3. Ignoring cultural and language variance. Emotion expression is culturally coded. A model trained on US English will mis-read Japanese, Indian or Russian customer affect. Multilingual fine-tuning is mandatory for any non-English deployment.

4. Skipping the consent UX. “By continuing this call you agree…” is not consent for biometric processing under GDPR Article 9. You need an explicit, separable, freely-given action — usually an extra click or an audio prompt.

5. Letting the model replace training. Emotion analysis detects frustration; it doesn’t teach empathy. The product wins when it’s a coaching tool for humans, not a substitute for them.

KPIs — how to measure emotion analysis is working

Quality KPIs. Macro-F1 across the 6–7 emotion classes (target ≥ 0.65 on real customer audio); per-class precision for “negative” and “frustrated” (target ≥ 0.75); calibration error, ECE (target < 0.10); and a cross-language parity gap under 10 points between English and your top non-English language.

Business KPIs. CSAT lift on AI-triaged calls vs a control group (target +10 points); escalation-resolution time delta (target −15%); 30-day churn delta on at-risk-flagged customers (target −20%); first-contact resolution (target +5 points).

Compliance KPIs. Consent-capture rate (target 100% of analysed calls); biometric-data retention (auto-delete ≤ 30 days unless legal hold); DPIA refresh (annually plus on every model update); and incident-free quarters with zero data-subject complaints.

Privacy, ethics and the customer trust contract

Beyond the law there’s a trust contract. Customers tolerate emotion analysis when it visibly helps them and visibly respects them; they push back hard when it surveils them. The product principles we apply on every build are plain.

Transparency. The customer is told, in plain language, that their voice and video may be analysed for service quality — before the call, not buried in legal small print. A visible “AI-assisted call” indicator stays on through the conversation.

Minimisation. Process the smallest signal that delivers the value. Voice prosody before video. Aggregated trajectories before raw-frame storage. Auto-delete raw biometrics within 30 days unless there’s a legal hold.

Reversibility. Customers can opt out without losing service quality. Models retrain without the opted-out customer’s data. Audit logs survive any opt-out.

Human in the loop. AI signals are advisory; the escalation, dispute or refund decision stays human. That’s also the cleanest defence against the next wave of regulator attention.

When NOT to ship video emotion analysis

Don’t ship workplace emotion analysis in the EU. The AI Act prohibition is unambiguous and the penalty is severe. Re-scope to customer-side or pick a different feature.

Don’t ship hiring or candidate-evaluation emotion analysis. Banned in the EU, BIPA-exposed in Illinois, scientifically thin everywhere. The reputational risk alone outweighs the upside.

Don’t ship “deception detection” via microexpressions. The science doesn’t support it and the lawsuits already filed will price you out.

Build vs buy — where Fora Soft fits

Buy off-the-shelf when: under 5M calls/year, English-dominant, no on-prem mandate, light compliance lift, and you can live with shared-tenancy data residency.

Build custom when: past 5M calls/year and the per-call SaaS bill tops an in-house GPU cluster; you’re in healthcare, finance, insurance or government; your data must stay on-prem or in-region; you need to fine-tune on industry vocabulary; or your business model depends on owning the IP. On-prem at contact-centre scale is a real pattern. For Nucleus, an on-prem communication platform, we built AI phone agents handling 600M+ call minutes a month under SOC 2, GDPR and HIPAA.

Verticals that almost always need custom: telehealth (HIPAA + GDPR Article 9), forensic interviewing (chain of custody), financial complaint handling (regulator scrutiny), insurance claim review, law-enforcement training simulators, and K-12 tools bound by FERPA. Our AI integration service is where those builds start.

Honest cost shape. A regulated-grade emotion analysis MVP runs from $120–$220K with our team using Agent Engineering; comparable integrators tend to quote $400K+ and 9–12 months. Where the scope needs face + voice + text, multilingual, or a full HIPAA/GDPR posture, we run a fixed-price discovery sprint first instead of guessing at a total.

Where customer-service emotion analysis spend is going

Spend is consolidating into the big CX suites. Verint bought Cogito in October 2024, Invoca bought Symbl.ai in May 2025, NiCE closed its Cognigy deal in September 2025, and Thoma Bravo took Verint private on 26 November 2025 and merged it with Calabrio under the Verint name. Standalone emotion APIs went the other way: Hume closed its Expression Measurement API on 14 June 2026 and ends EVI and TTS API access on 13 November 2026.

For a buyer this means two things. Emotion signals increasingly arrive as one feature inside a CCaaS or QA suite, and any standalone API you build on needs an exit plan. Headline market-size figures vary widely with the definition; we keep them, with sources, in our emotion detection software comparison and market estimates. If you’re placing a bet, place it on the customer-side, consent-first side of the EU line.

FAQ

What’s the difference between emotion analysis and sentiment analysis?

Sentiment analysis scores polarity (positive, negative or neutral), usually from text. Emotion analysis is finer-grained: it identifies specific states like anger, fear, frustration or joy, and often reads them from voice and face as well as words. In customer service, sentiment tells you a call went badly; emotion analysis tells you it went badly because the customer was anxious rather than furious, which changes how you route it.

What is video emotion analysis in customer service?

It’s the real-time reading of a customer’s emotional state from a video stream — face, voice and optionally text — to drive supervisor alerts, post-call quality analytics, churn prediction and CSAT prediction. The pipeline is multimodal: facial computer vision plus voice prosody plus text sentiment, fused on a server-side or edge inference cluster.

Is workplace emotion analysis legal in the EU?

No, with narrow exceptions. Article 5(1)(f) of the EU AI Act prohibits inferring emotions of people in workplace and education settings from 2 February 2025; only medical and safety reasons (such as driver fatigue) are allowed. Penalties reach €35M or 7% of global turnover and became enforceable on 2 August 2025. Consent does not cure it. Customer-side analysis with a lawful basis under GDPR Article 9 stays permissible. Since 2 August 2026, Article 50(3) also requires telling customers when emotion recognition is applied to them.

How accurate is emotion analysis on real customer calls?

Around 50–75% on broad emotion classes, well below the 90%+ vendor demos suggest. Public benchmarks are optimistic and inconsistent (RAF-DB ~92%, FER2013 ~75%, AffectNet ~65%) and drop 10–25 points on real customer audio and video. Treat the output as a triage hint, not a verdict, and pair it with text keywords to cut the false-positive rate from 5–10% to under 2%.

Which platform should I pick in 2026?

Voice and text in a contact centre: Verint (with Cogito’s real-time scoring), NiCE Enlighten, Observe.AI, Uniphore or Invoca (which bought Symbl.ai in 2025). Face channel for consented video, research or training: Smart Eye/Affectiva, iMotions, Noldus FaceReader, or MorphCast in the browser. AWS Rekognition covers expression cues inside an AWS estate. Avoid new builds on Hume, whose EVI API closes on 13 November 2026; Microsoft retired Azure Face emotion in 2022.

How much does emotion analysis cost per call?

$0.05–$0.30 on SaaS depending on modality and volume. Voice-only lands at $0.08–$0.15/call; video-plus-voice multimodal at $0.20–$0.30. Volume discounts are aggressive: 50M-call/year contracts approach $0.05/call. A custom build breaks even with SaaS near 5M calls/year for regulated workloads.

When should I build custom instead of buying SaaS?

Build when you’re past ~5M analysed calls/year, in healthcare, finance, insurance or government, on-prem or EU residency is mandatory, you need multilingual or industry-vocabulary fine-tuning, or you’re selling emotion analysis as a product feature. Below those thresholds SaaS wins on every axis except IP ownership.

What about Illinois BIPA, Texas CUBI and California CPRA?

BIPA requires written informed consent and a documented retention policy for face and voice biometrics, and its private right of action makes class actions a real risk. Texas CUBI is similar but AG-enforced only. CPRA classifies biometrics as sensitive personal information with deletion and opt-out rights. Treat US biometric law as fragmented and design to the strictest state in your footprint.

Is there a tool that detects emotional distress or harassment in customer service calls automatically?

Yes. Contact-centre speech-analytics suites such as Verint, NiCE Enlighten and Observe.AI score sentiment on calls and flag escalation risk in real time; abusive or harassing language is usually caught by a classifier on the transcript rather than by tone alone. In a custom build, pair voice prosody with an LLM or keyword classifier on the transcript and route every flag to a supervisor, not to an automatic action.

What is the best contact centre software for real-time customer emotion detection?

For voice in an existing contact centre, shortlist Verint, NiCE Enlighten, Observe.AI and Uniphore, then pick the one that plugs into your CCaaS and can be limited to the customer channel in the EU. Build custom when you need on-prem hosting, multilingual tuning, a video channel or ownership of the model.

How do you analyze emotion in product usage videos?

Record sessions with explicit consent, run facial coding (iMotions, Smart Eye/Affectiva or Noldus FaceReader) alongside the think-aloud audio and screen events, and compare emotion shifts at specific product moments rather than session averages. That is UX research rather than customer service; our guide to machine learning tools for video emotion recognition compares the options.

Which platforms measure emotional reactions to packaging on video?

Consumer-research platforms built on facial coding: Smart Eye/Affectiva media analytics, iMotions and Noldus FaceReader are the established ones. They track moment-by-moment expression and attention while a consented panel watches a pack shot or ad; read the result as a comparison between variants, not as an absolute emotion score.

Can emotion analysis replace agent training?

No. Emotion analysis detects frustration; it doesn’t teach empathy. Deployments that try to replace human empathy with scripted “I understand you’re upset” responses tend to see CSAT fall, not rise. Use it as a coaching tool for humans, not a substitute.

What to Read Next

Ready to ship emotion analysis, honestly?

Video emotion analysis for customer service is a real capability in 2026, not a research demo. The decisions that separate a good rollout from a regulatory or accuracy mess are the same ones we walk clients through: customer-side only inside the EU, multimodal fusion to lift accuracy, voice before video, consent baked into the UX, and false-positive calibration before any alert hits an agent screen.

If you’re past those decisions and into build vs buy, we’ve done both ends — integrating voice-prosody vendors for one team, building a regulated multimodal pipeline for another. Bring the use case; we’ll bring the architecture, the regulatory map and an honest scope.