It's 6:05 AM and there's a ransom note on the screen. Blake knows what to do first.
LoDo IT keeps its support desk open from 8 to 6 Mountain on weekdays. Blake covers the hours around that and the questions nobody has time for between tickets. He opens tickets, points clients to the right tool, gives calm first steps when something looks like an attack, and books prospects a call with Brandon. He never takes a password, never resets anything himself, and never guesses at a price.
Blake's board, this visit
On duty- 0
- Tickets opened
- 0
- Security steps
- 0
- Leads in Loop
- 0
- Brief items
- Play a scenario below and watch this fill up.
Four moments in a week at an MSP.
Pick one. On the left, how LoDo IT is reached today. On the right, Blake. Watch what's still waiting for the team when each one ends.
Dana Ortiz, office manager at Tamarack Family Dental (demo). Dana's first patients check in at 8. The front-desk printer won't print intake forms, and while she's waiting she has a HIPAA question that's been bugging her for a week.
How LoDo IT is reached today
A chat widget, a contact form, and voicemail after 6 PM
Blake
AI front desk and IT guide, working in Loop, Autotask (demo), the calendar and texts
Every person, company, phone number, ticket number and time here is invented for the demo. Tickets are labeled Autotask (demo) and nothing touches LoDo IT's real systems. The client tool links are the real ones from lodoit.com. Blake gives general compliance information and never certifies anyone; your auditor or assessor makes the call.
Pick a role. Talk to Blake. Watch the back office move.
Call Blake as Dana
Uses your microphone. Speak naturally. Interrupt him any time.
Conversation
Start a call and the transcript appears here. Blake opens with a short greeting, then it's your turn.
What Blake did
Tickets, leads, bookings and notes for Brandon land here the moment Blake makes them.
Blake works on a sample back office here. Nothing touches LoDo IT's real clients, tickets, Autotask, ScreenConnect, billing or spam filter.
Everything since last night, before the first ticket.
The incident first, then the urgent lockout, then the new lead, then what Blake couldn't answer. Two decisions only Brandon can make. Try the buttons.

Blake at LoDo IT
to Brandon · 7:00 AM
Monday, November 23
Good morning, Brandon.
One security incident before dawn, one urgent lockout from Sunday, one new co-managed lead, and four questions I couldn't answer. The incident is first.
Needs you
Take the Union Loaf Bakery incident yourself, or hand it to a tech?
Jordan Lee isn't a client yet. The office computer shows a ransom note and the shared drive is renamed. The machine is disconnected and powered on. No money was sent.
Blake recommends a call before 7:30. Jordan has been waiting since 6:05 and has been told not to touch anything.
Confirm Tuesday 9:30 with Marcus Hale?
Platte Yard Builders (demo), 45 seats, one in-house IT person. He asked for Tuesday between nine and eleven. Your calendar is open at 9:30.
Blake recommends 9:30 and asking for the insurance questionnaire ahead of time.
Overnight
- 6:05 AMUrgent. Jordan Lee, Union Loaf Bakery (demo), new contact, 6 seats: ransom note on the office computer, shared-drive files renamed. First steps given. The machine is unplugged and still on, nothing paid, nothing deleted. Incident IR-208, ticket TK-2049. Jordan is waiting at 303-555-0164.
- 4:30 PM SunUrgent. Priya Raman, Raman & Cole (demo), locked out of her email before a filing today. She offered her old password; I declined it and didn't record it. Ticket TK-2046 needs someone to verify her by phone before any reset.
- 8:45 PM FriNew lead, LD-3007. Marcus Hale, Platte Yard Builders (demo), 45 seats, two Denver offices, one in-house IT person named Kevin. Looks like co-managed. Insurance renewal is asking about MFA and backups. He asked for Tuesday morning.
- This weekGaps to teach in the Studio: what LoDo IT charges, response times, the after-hours policy, and which security tools I may name. I said you'd follow up each time and didn't guess.
17
Calls and chats since Friday
5
Tickets opened
2
Urgent items
1
New leads in Loop
On your calendar
- 8:00 AMRaman & Cole lockout: verify Priya by phone, then reset (TK-2046)
- 9:00 AMCheck in on Union Loaf Bakery (IR-208)
- Tue 9:30 AMDiscovery call with Marcus Hale, if confirmed
Blake is handling
- Keeping Jordan's number at the top of the urgent list
- Sending Dana Ortiz the ticket portal link when she asks
- Holding the insurance questions for Marcus's call
- Listing the four open gaps in the Studio until you answer them
He remembers the business, not the passwords.
Seats, offices, the in-house IT person, the insurance renewal, the time that works. When a prospect comes back, nobody asks them to start over. Credentials and health details are never kept.
What Blake knows about Marcus
- Platte Yard Builders (demo), 45 seats, two Denver offices
- In-house IT: Kevin, who stays; co-managed is the fit
- Cyber-insurance renewal is asking about MFA and backups
- Discovery call with Brandon, Tuesday 9:30 AM
- Prefers text; mornings work best
Marcus and Platte Yard Builders are invented for the demo. Nobody typed this into a form. It came from one chat and one call, and it's open before he finishes saying hello. Blake keeps business details only: no passwords, no codes, nothing a client wouldn't say out loud.
Two visits, one thread
- Thu 8:45 PMLoop CRM
First chat from the website. 45 people, two Denver offices, one in-house IT person named Kevin who is stretched thin. Blake read it as co-managed and said so in plain words.
- Thu 8:49 PMStudio
Marcus asked for a ballpark price. Blake didn't have a LoDo IT number and said so. The pricing question went to Brandon as a gap to teach.
- Thu 8:51 PMCalendar
Discovery call with Brandon requested for Tuesday morning, nine to eleven. Brandon confirmed 9:30 the next day and Blake texted Marcus, with his permission.
- Mon 10:12 AMPhone
Marcus called back with a question about the insurance form. Blake greeted him by name, remembered Kevin and the renewal, and added the question to Tuesday's call notes instead of starting over.
A real technician is better. Blake covers the other hours.
During business hours LoDo IT's technicians answer the phone and fix things, and nothing beats that. Before 8, after 6 and on weekends, today it's voicemail and a chat widget that may or may not be watched. Blake fills that gap and leaves the fixing to the people who do it.
Answers at 6 AM or on a Sunday
How LoDo IT is reached today
Voicemail; chat if someone is watchingBlake
Phone and chat, any timeFixes the problem
How LoDo IT is reached today
A LoDo IT technicianBlake
Never. He opens the ticket; a technician fixes itTalks to a real technician
How LoDo IT is reached today
During business hours, ext 2Blake
Hands off to one, or flags it urgent after hoursOpens a ticket
How LoDo IT is reached today
Client portal or email, if you remember whereBlake
On the call, with the details already in itPoints clients to the right tool
How LoDo IT is reached today
The Customer Portals menuBlake
Remote support, tickets, billing or spam filter, in one lineRefuses passwords and codes
How LoDo IT is reached today
Up to whoever answersBlake
Every time, every channel, even for known clientsFirst steps in a ransomware scare
How LoDo IT is reached today
When the office opensBlake
Disconnect, don't pay, don't delete, then urgent handoffAsks prospects about the business first
How LoDo IT is reached today
A form with a message boxBlake
Seats, offices, in-house IT, compliance, renewalExplains managed vs co-managed
How LoDo IT is reached today
Brandon, on a callBlake
In plain words, then books the call with BrandonGives a price
How LoDo IT is reached today
After a discovery callBlake
After a discovery call; never guessesAnswers compliance questions
How LoDo IT is reached today
The team, when there's timeBlake
General answers; never certifies anyoneRemembers a prospect on the second visit
How LoDo IT is reached today
If the form reached the right inboxBlake
Seats, people, what hurts, open before helloLeads land somewhere they won't get lost
How LoDo IT is reached today
An email inboxBlake
Loop, with the next stepTells Brandon what he still needs to teach
How LoDo IT is reached today
Nobody keeps that listBlake
Gaps in the Studio and the morning brief
| The job | How LoDo IT is reached today | Blake |
|---|---|---|
| Answers at 6 AM or on a Sunday | Voicemail; chat if someone is watching | Phone and chat, any time |
| Fixes the problem | A LoDo IT technician | Never. He opens the ticket; a technician fixes it |
| Talks to a real technician | During business hours, ext 2 | Hands off to one, or flags it urgent after hours |
| Opens a ticket | Client portal or email, if you remember where | On the call, with the details already in it |
| Points clients to the right tool | The Customer Portals menu | Remote support, tickets, billing or spam filter, in one line |
| Refuses passwords and codes | Up to whoever answers | Every time, every channel, even for known clients |
| First steps in a ransomware scare | When the office opens | Disconnect, don't pay, don't delete, then urgent handoff |
| Asks prospects about the business first | A form with a message box | Seats, offices, in-house IT, compliance, renewal |
| Explains managed vs co-managed | Brandon, on a call | In plain words, then books the call with Brandon |
| Gives a price | After a discovery call | After a discovery call; never guesses |
| Answers compliance questions | The team, when there's time | General answers; never certifies anyone |
| Remembers a prospect on the second visit | If the form reached the right inbox | Seats, people, what hurts, open before hello |
| Leads land somewhere they won't get lost | An email inbox | Loop, with the next step |
| Tells Brandon what he still needs to teach | Nobody keeps that list | Gaps in the Studio and the morning brief |
The left column describes how lodoit.com works as of November 19, 2026: a Tawk.to chat widget, a contact form, and phones answered 8 AM to 6 PM Mountain, Monday to Friday, with voicemail after hours. Whether the chat is staffed after hours wasn't verified. Blake doesn't replace the technicians; he covers the hours around them and keeps the details straight.
Autotask stays. ScreenConnect stays. The voicemail backlog goes away.
01
Teach
We load LoDo IT's services, client tools and the guardrails. Brandon teaches Blake the rest in the Studio in his own words: pricing, response times, the after-hours policy, which security tools to name. His answers outrank everything.
02
Shadow
Blake takes the chat and an after-hours line. Brandon reads every conversation and every ticket he opens. Anything he can't answer lands in the brief as a gap, never a guess.
03
Hand off
When Brandon trusts him, Blake takes the first conversation. Leads land in Loop, tickets in Autotask, urgent items reach the right person, and technicians still do every fix.
Built for LoDo IT by ATERNA AI.
We build AI front desks for companies whose people are too busy doing the work to answer every call. Fifteen minutes is enough to see whether Blake fits.
