Multilevel support teams
Influx provides fully managed Customer Support and Technical Support teams, scoped to the right level of complexity for your product.
Customer support vs technical support
First, decide if you need someone to primarily talk with your customers or diagnose technical issues.
Customer support
Owns customer resolution
When the customer needs help using the product
- Questions, guidance & clarification
- Order status & account support
- Policy interpretation & standard workflows
"How do I...?" · "What should I do?"
✓ CS = Resolve the situation
Technical support
Owns system diagnosis
When something is not working as expected
- Something broken or behaving unexpectedly
- Troubleshooting & investigation required
- System behaviour, configs & integrations
"This doesn't work" · "Something is wrong"
✓ Tech = Diagnose and resolve system issues
Both Customer Support and Technical Support teams resolve customer issues across multiple levels of complexity. L1, L2, and L3 refer to Level 1, Level 2, and Level 3 Customer Support respectively — while T1, T2, and T3 refer to the equivalent levels within Technical Support.
Three Levels of Complexity
Support levels (L1–L3)
Complexity drives the level — not titles. One consistent model across customer and technical support.
L1 / T1
Follow the playbook
Is the work predictable? Do clear steps exist to resolve it?
Customer Support
- FAQs, policy clarifications
- Order status, standard updates
- Escalates anything non-standard
Technical Support
- Known login / setup issues
- Step-by-step troubleshooting
- Escalates unclear root causes
L2 / T2
Apply the playbook
Does it need investigation or interpretation within known rules?
Customer Support
- Refunds & changes needing validation
- Multi-step resolution with judgment
- Identifies recurring patterns
Technical Support
- Config, permissions, integration issues
- Cross-system investigation
- Structures recurring failure patterns
L3 / T3
Change the playbook
Is the root cause unclear or outside known systems?
Customer Support
- High-risk / ambiguous edge cases
- Defines new workflows & policies
Technical Support
- Unknown / complex system failures
- Root cause analysis (logs, APIs)
⚠ Influx focuses on L1/L2 and T1/T2. L3/T3 is better handled internally.
Key rule:
Predefined workflow?→ L1 / T1
Needs investigation?→ L2 / T2
Expert-level / unknown?→ L3 / T3 (internal)
Customer Support
L1 vs L2 — What's the difference?
Both levels resolve customer situations — L1 follows a defined workflow, L2 applies judgment when the situation requires investigation.
CS L1 — Follow the playbook Known, repeatable, workflow-driven
CS L2 — Apply the playbook Investigate, interpret, use judgment
Primary Role
Help the customer move forward using pre-defined workflows — no ambiguity required.
Typical Actions
- Answer FAQs and policy questions
- Process order status requests
- Apply standard resolution workflows
- Escalate anything non-standard to L2
✓ Issue resolved using existing playbook
Primary Role
Investigate customer issues using judgment within known rules — when a clear workflow doesn't exist.
Typical Actions
- Validate refunds & account changes
- Check payment status and account history
- Multi-step resolution with judgment
- Identify & structure recurring patterns
✓ Issue resolved — situation handled with judgment
L1 ExampleCustomer asks to change delivery address right after ordering → agent follows policy and updates.
L2 ExampleCustomer charged twice, one payment pending → agent checks system, validates, decides whether to refund or wait.
Technical Support
T1 vs T2 — What's the difference?
Both levels diagnose and resolve system issues — T1 follows structured diagnostic workflows, T2 investigates deeper across systems and integrations.
Tech T1 — Follow the playbook Known issues, structured diagnosis
Tech T2 — Apply the playbook Cross-system investigation, deeper analysis
Primary Role
Diagnose and resolve known system issues using structured diagnostic workflows.
Typical Actions
- Follow step-by-step diagnostic flows
- Reproduce known issues
- Verify system behaviour against known patterns
- Fix or escalate with clear diagnosis
✓ Issue resolved and clearly diagnosed
Primary Role
Investigate complex system issues across tools, configs, and integrations requiring deeper analysis.
Typical Actions
- Investigate configs, permissions, integrations
- Cross-system investigation
- Review payment logs & transaction data
- Identify & structure recurring failure patterns
✓ Issue resolved or scoped — escalation path clear
T1 ExampleUser can't log in, error matches known issue → agent follows diagnostic steps, confirms root cause.
T2 ExamplePayments failing for a specific region → agent investigates configs, payment provider, identifies the pattern.
CS L2 vs Tech T1 — what separates them? They can look similar in ability but serve different outcomes. CS L2 resolves the customer's situation. Tech T1 also troubleshoots the underlying system issue and confirms or escalates the root cause. Same empathy, different mandate. See FAQ for the full breakdown →
Scoping Guide
Not sure what you need?
Answer four questions and we'll map your support need to the right product and level.
| Question | Answer → Outcome |
|---|---|
| 1. What type of problem is this? | Usage / guidance → Customer Support Something broken → Technical Support |
| 2. Do clear workflows already exist to handle it? | Yes → L1 / T1 No → Go to Q3 |
| 3. Can workflows be created and agents trained quickly? | Yes → L1 / T1 (+ Shared Team Leader) No → Go to Q4 |
| 4. Does it require investigation or deep expertise? | Investigation within known system → L2 / T2 Unknown / complex → L3 / T3 (internal) |
FAQ
Frequently asked questions
More detail on how the framework works in practice.
What's the difference between Customer Support and Technical Support? ▾
CS helps customers use your product — answering questions, applying policy, and resolving issues. Tech Support diagnoses when something isn't working — investigating system behaviour, configs, and integrations. Both may talk to users, but with different objectives.
What's the difference between L1 and L2 Customer Support? ▾
L1 follows a defined playbook for known, repeatable issues. L2 applies the playbook using judgment — when the situation needs investigation or interpretation within known systems and policies.
What's the difference between T1 and T2 Technical Support? ▾
T1 follows structured diagnostic workflows for known system issues. T2 investigates more complex problems — cross-system, multi-integration, or requiring deeper root cause analysis.
CS L2 and Tech T1 sound similar — what actually separates them? ▾
They can look similar in ability but serve different outcomes. CS L2 resolves the customer's situation — getting them to a satisfactory next step. Tech T1 also troubleshoots the underlying system issue and confirms or escalates the root cause. Tech T1 agents follow diagnostic flows; CS L2 agents apply policy and judgment.
Do you offer L3 / T3 support? ▾
Influx focuses on L1/L2 and T1/T2. L3/T3 involves complex unknowns, root cause analysis, and product/engineering collaboration — work better handled by your internal team. We'll flag when escalation is needed and structure handoffs clearly.
Can I use both Customer Support and Technical Support? ▾
Yes — many Influx clients run both in parallel. Your CS team handles usage questions and account issues, while the Tech team manages system diagnosis and escalations. We'll scope and staff both as part of a single managed operation.
How do you onboard and train agents on our product? ▾
Onboarding typically takes one week. We use your documentation, existing workflows, and product knowledge to train agents before they go live. We build playbooks for L1/T1 and escalation paths for L2/T2 as part of the setup process.
What channels do your agents support? ▾
Influx agents work across email, live chat, social media, and voice. We integrate directly with your existing help desk or platform — no migration required.
 6 Circle - small.png)