Services

It is game week. A venue has an open display issue, a scheduled event, and a client asking whether the site is ready. You need the Company, tickets, recent activity, and service notes in one place — and you need them before the client calls, not after.

That is what this track teaches: the working rhythm that keeps every venue you cover readable at a glance, so readiness is something you know, not something you go find out.

Click to enlarge

What You Are Trying To Do

This track is for service contracts, maintenance, field operations, and venue support.

You are learning how to:

1. Track what's broken - create, assign, escalate, and close tickets.
2. See the full venue story - Company, contacts, contracts, opportunities, tickets, notes, and history.
3. Check venue health - recent activity, recurring service, event context, and outstanding issues.
4. Keep the handoff clean - make sure the next person can see status without hunting.

None of these are new skills — you already do this work. What changes is where the record lives. When status lives on the venue instead of in your inbox, a colleague can cover your venue mid-shift, leadership can answer a client without pinging you, and nothing depends on you remembering it.

Two surfaces, one story

You work across two connected surfaces, and knowing which one is "home" for each kind of work is half the track:

• The Service Dashboard is the working surface — tickets, events, staffing, game-day workflows, and field operations live here. When something breaks, gets scheduled, or gets fixed, this is where it happens.
• The CRM is the relationship surface — the Company record, contacts, deals, contract scope, and the full account history live here. This is where you read a venue before a call or a visit.

The bridge between them is Real-time CRM Sync. When a ticket is opened, updated, or closed in the Service Dashboard — or an event is scheduled, or a technician moves through the game-day workflow — the change appears on the CRM Company page in about a second. You never copy anything across, and you never wonder which version is current. Work where the work lives; read where the relationship lives.

Click to enlarge

Day 1 / Day 30 / Reference

• Day 1: open the Company, find open tickets, check event context, and read the latest note.
• Day 30: spot venue health patterns, overdue issues, repeated failures, and handoff gaps.
• Reference as needed: IoT Operations Workspace, walkthroughs, maintenance records, reports, portals.

The Day 30 skill is the one that matters. Anyone can read one ticket. The operator-level skill is reading a venue: the same display failing three times in two months, a ticket that has sat unowned since last week, an event on Saturday with an unresolved issue in front of it. That pattern reading is what this track builds toward.

Ask the assistant

Every lesson in this track shows two paths — the click path and the ask path. Scout can pull the same picture for you in one line:

Use whichever path is faster in the moment. Field crews on a phone tend to ask; anyone already in a list view tends to click. Both read the same live data.

What You'll Learn Here

1. Track service tickets - creating, assigning, tracking, and escalating tickets, and how they tie to the Company.
2. Read the Company view - seeing every venue, contact, contract, and open item in one place.
3. Check venue activity - history, logging site visits, and recurring service.
4. Run the day-to-day queue - the views and habits that keep nothing falling through the cracks.

Take them in order the first time — tickets are the raw material, the Company view is where they become a story, activity is how the story stays current, and the day-to-day lesson turns all of it into a habit. After that, each page stands alone as a reference.

The quality bar

You are done with this track when, for any venue you cover, you can answer four questions in under a minute without asking anyone:

1. What is open right now, and who owns each item?
2. What is happening at the venue this week?
3. What happened the last time we were on site?
4. What did ANC sell this account, and who are the people we deal with?

If any answer requires digging through email or memory, the record is not current — and fixing that is the job.

Quick Glossary

• Service Ticket - an issue tied to a venue or Company.
• Event - scheduled venue activity.
• Walkthrough - a site visit or readiness check.
• IoT Operations Workspace - the structured operations workspace for venue data.

Haven't done Core yet? Start there first: Core — Start Here.