L1 support is the first human contact for every question, error report and request your users send. Codersarts runs your first-line technical support desk: we receive tickets, record them properly, set priority, solve known issues from your runbook, and pass everything else upward with the evidence engineers need. Your users get fast, consistent answers, and your developers stop being interrupted by password resets.
At a Glance
Item | Details |
|---|---|
What it covers | Ticket intake, triage, priority, known fixes, escalation |
Channels | Email, web form, chat, Slack, Microsoft Teams, or your ticketing system |
Who does the work | Trained support engineers working from your runbook |
Escalates to | L2 application support, inside Codersarts or your own team |
Pay-as-you-go rate | USD 25 per hour, prepaid in 10-hour blocks |
Included in | Essential, Growth and Dedicated Team plans |
Hours | Business hours in your timezone, with extended options |
What Is L1 Support?
L1 support, also called first-line or Tier 1 support, is the first level of technical support. It receives every incoming issue, collects the details, sets priority, resolves problems that have a documented fix, and escalates anything more complex to L2 with the information needed to continue without asking the user again.
A good L1 team is not a call centre reading scripts. It is the filter that decides how quickly a real problem reaches an engineer, and how much engineering time is wasted on issues that never needed one.
The goal of L1 is simple: solve what can be solved quickly, and hand over everything else so well that nobody has to ask the user the same question twice.
What L1 Handles
User Questions and Access
How-to questions about features, settings and workflows
Login problems, password resets and locked accounts
User role and permission changes within agreed rules
Questions about data exports, reports and notifications
Known Issues From the Runbook
Restarting a stuck service or worker using documented steps
Re-running a failed scheduled job when the runbook allows it
Clearing a queue, cache or session using approved procedures
Applying documented workarounds while a permanent fix is planned
Monitoring and Alert Checks
Confirming whether an uptime or error alert reflects a real problem
Checking status pages of third-party services, such as payment or mapping providers
Recording false alarms so alert thresholds can be improved
Logging and Communication
Creating a ticket for every issue, with category, priority and affected users
Keeping users informed about progress and expected next steps
Closing tickets with a clear summary of what was done
What L1 Does Not Handle
Clear boundaries keep L1 fast. These go straight to the next level:
Investigating errors in logs, databases or integrations, which is L2 Support
Any change to code, database structure or configuration, which is L3 Support
Full outages, data loss and security incidents, which are led by L4 Support
How an L1 Ticket Flows
Intake. The issue arrives through an agreed channel and becomes a ticket with a unique reference.
Classification. L1 records the category, affected users, device or browser, and the exact error text.
Priority. L1 applies your written priority rules, so a payment failure is never queued behind a typo.
Runbook check. If a documented fix exists, L1 applies it and confirms with the user.
Escalation. If not, L1 escalates with a complete handoff note.
Follow-up. L1 keeps the user updated and closes the ticket once the fix is confirmed.
What a Good Escalation Contains
Poor escalations are the biggest hidden cost in support. Engineers lose time asking for details the first contact should have captured. Every Codersarts L1 escalation includes:
What the user was trying to do, in their words
The exact error message or screenshot
Time of the problem, with timezone
Affected users, accounts or records
Steps already tried and their results
Priority with the reason it was chosen
Priority Rules L1 Applies
Priority | Meaning | Example | L1 action |
|---|---|---|---|
Critical | Core service unavailable for many users | Nobody can log in | Escalate immediately and alert the on-call engineer |
High | Important feature broken, workaround exists | Reports failing to export | Escalate within the hour with full details |
Normal | Problem affects some users or a minor feature | Wrong date format in one screen | Escalate during the same business day |
Low | Question or small request | Change a label | Resolve or schedule |
Priority definitions are agreed with you during onboarding and written into your runbook.
Runbook and Knowledge Base
L1 is only as strong as its runbook. During the Application Support Assessment we document known issues and their fixes. After that, every resolved L2 or L3 ticket is reviewed: if the fix can be safely repeated, it becomes a new runbook entry. Over time, more issues are solved at L1, response gets faster and your support costs fall.
We can also turn runbook entries into user-facing help articles, so users solve common problems themselves before raising a ticket.
Metrics We Report
Metric | What it tells you |
|---|---|
First response time | How quickly users hear back |
First-contact resolution | Share of tickets solved without escalation |
Escalation rate | How many tickets need L2 or higher |
Escalation quality | How often engineers had to ask for missing details |
Reopen rate | How often fixes did not hold |
Ticket volume by category | Where users struggle most, to guide product fixes |
These appear in your monthly support report alongside hours used.
L1 Compared With L2 Support
Factor | L1 Support | L2 Support |
|---|---|---|
Main job | Receive, sort, fix known issues, escalate | Investigate and fix application problems |
Skills | Product knowledge, communication, runbook use | Logs, databases, APIs, configuration |
Changes made | None outside documented procedures | Configuration and small fixes |
Typical ticket time | Minutes | Hours |
Hourly rate (pay-as-you-go) | USD 25 | USD 55 |
When to Outsource L1 Support
Your developers answer user questions instead of building the product
Tickets arrive in personal inboxes and chat messages with no tracking
Users wait a day for answers to simple questions
You are launching to new markets and need support across more hours
You resell or deliver software to clients who expect a professional support desk
Working With Your Existing Tools
We work inside the tools you already use, including Zendesk, Freshdesk, Jira Service Management, HubSpot, Intercom, Help Scout and shared inboxes. If you have no ticketing system, we can set up a simple one during onboarding so every request is tracked from day one.
Common L1 Ticket Categories
Category | Typical examples | Usually resolved at |
|---|---|---|
Access | Password reset, locked account, two-factor problems | L1 |
How-to | Where to find a setting, how to export data | L1 |
Data questions | Missing record, unexpected value, report totals | L1 checks, L2 investigates |
Errors | Error message on a screen, failed upload | L1 collects evidence, L2 fixes |
Notifications | Emails or alerts not received | L1 checks settings, L2 checks delivery logs |
Integrations | Data not syncing with another system | L2 |
Outages | App not loading, many users affected | Escalated immediately |
Communication Standards
How users are spoken to affects how they feel about your product as much as how fast the fix arrives. Codersarts L1 engineers follow written standards agreed with you:
Plain language. No internal jargon or blame on the user.
Your tone of voice. Formal or friendly, matching your brand guidelines.
Honest timing. Users are told what happens next and when, not given vague promises.
No silent tickets. Every open ticket receives a status update within the agreed time, even if there is no news yet.
Clear closure. Tickets close with a summary of the cause and what to do if it happens again.
We can work under your brand name, so users see your support desk rather than an outside company.
How L1 Lowers Your Engineering Costs
Every simple question that reaches a developer costs more than it should. The developer stops their task, reads the message, asks for details, waits, answers, and then needs time to get back into focused work. A trained L1 desk removes most of that disruption:
Routine questions never reach engineers
Escalations arrive complete, so investigation starts immediately
Duplicate reports of the same problem are grouped into one ticket
Repeated issues are spotted early and reported as product problems to fix
The result is fewer interruptions for your product team and faster, more predictable answers for users.
In-House or Outsourced L1: Which Is Better?
Factor | In-house L1 hire | Codersarts L1 support |
|---|---|---|
Time to start | Weeks to recruit and train | Days after the support assessment |
Coverage gaps | Holidays and sick days leave the desk empty | Backup engineers cover absences |
Technical depth behind L1 | Depends on your developers | L2 to L4 engineers in the same team |
Cost | Full salary, tools and management time | Hours used, from USD 25 per hour |
Best for | High, steady volume needing deep product immersion | Growing products, variable volume, extended hours |
Many companies start with outsourced L1, learn their real ticket patterns, and decide later whether to bring the desk in-house. Because the runbook and ticket history belong to you, that move is straightforward.
Turning Tickets Into Product Insight
L1 sees every complaint before anyone else. Each month we group tickets by feature and cause, and highlight the screens, workflows and error messages that generate the most questions. Product teams use this to fix confusing design, improve wording and prioritize bugs that affect the most users.
Onboarding Checklist for L1
Agree support channels, hours and the ticketing tool
Write priority definitions and escalation rules
Collect existing help articles, FAQs and known issues
Set up L1 access to the admin panel, monitoring and status pages with least privilege
Shadow a sample of past tickets to learn common questions
Go live with daily check-ins during the first two weeks
Pricing
Option | What you get | Price |
|---|---|---|
Pay-as-you-go | L1 hours drawn from prepaid 10-hour blocks | USD 25 per hour |
Essential plan | L1 and L2 together, 10 hours per month | USD 499 per month |
Growth plan | L1 to L3, 25 hours per month, after-hours critical response | USD 1,299 per month |
See all plans on Support Levels. For automated first-line answers, add L0 AI Support.
Who Uses Codersarts L1 Support
SaaS founders without a dedicated support person
Product teams whose developers are handling too many user questions
Agencies that need a support desk for client applications
Operations teams running internal tools used across several departments
Frequently Asked Questions
What is L1 support?
L1 support is the first level of technical support. It receives issues, sets priority, fixes known problems from a runbook and escalates the rest to L2.
What is the difference between L1 and L2 support?
L1 handles first contact and documented fixes, while L2 investigates logs, data and integrations to find and fix the cause of a problem.
How much does outsourced L1 support cost?
Pay-as-you-go L1 support costs USD 25 per hour in prepaid 10-hour blocks, or it is included in plans starting at USD 499 per month.
Can you use our ticketing system?
Yes. We work in Zendesk, Freshdesk, Jira Service Management, HubSpot, Intercom, Help Scout or a shared inbox.
Will L1 make changes to our application?
Only through documented runbook procedures you approve, such as restarting a service. Code and configuration changes are handled by L2 and L3.
Can L1 escalate to our own developers instead of Codersarts?
Yes. We can escalate to your team, to Codersarts L2, or split escalations by type.
Do you provide L1 support outside business hours?
Yes. Extended hours and after-hours options are available through our support coverage plans.
How quickly can L1 support start?
Once the support assessment and runbook are complete, L1 can usually start within a few business days.
Give Your Users a Proper First Line of Support
Tell us how many users you support and where tickets arrive today, and we will design an L1 setup that fits your volume, hours and tools.
Back to Support Levels or explore Support Coverage.