Connected by purpose.
Working together for you.

Betty brings requests, priorities, communications, and follow-ups into one organized view. Her focus is coordination: giving each conversation a clear owner, bringing the right specialists into the discussion, and surfacing decisions that need Toby’s attention. Clear next steps and careful follow-through are central to her role, along with respect for approved communication rules and the commitments already made to customers and the team.

Outside work, Betty enjoys crosswords and cooking.

Jenna’s focus is turning field work into documentation that makes sense to the next person who reads it. Technician notes, photos, materials, and test results provide the foundation for a clear customer closeout. Completed work, outstanding issues, and missing evidence stay distinct, giving billing and future visits a useful handoff without treating installation, verification, invoicing, and payment as the same milestone.

Outside work, Jenna enjoys baking and scrapbooking. She has a soft spot for a well-tested recipe and the small details that make a good memory worth keeping.

Casey’s focus is scheduling readiness: making sure a job has the equipment, prerequisites, access, information, and suitable technician it needs. Customer availability and travel considerations belong in the same picture as the technical work. Clear readiness checks help expose conflicts before a visit is promised. Casey’s role supports Chelsea’s scheduling decisions; Chelsea retains final authority over confirmed appointments and technician assignments.

Outside work, Casey enjoys scuba diving, especially unhurried reef dives and discovering marine life. She likes the preparation as much as the dive: checking the gear, planning the route, and leaving time to enjoy the water.

Toby works hands-on with the technology that restaurants and businesses depend on: networks, Toast POS, Wi-Fi, cabling, cameras, communications, and backup internet. His work connects the technical details with what the business needs during a busy shift, a new opening, or an equipment problem. Practical troubleshooting, clear documentation, and a setup that can be supported afterward guide the work.

Alongside field work, Toby brings together the customer’s priorities, the technical approach, and the people needed to get the job done. The goal is technology that fits the operation, with a clear next step when something needs attention.

Troy is part of the Phoenix Geeks field team, working on onsite technical jobs, equipment installations, and troubleshooting. His role brings hands-on attention to the devices, connections, and site conditions that remote records do not always capture. Clear technician notes, photos, and test results make that field work useful to the customer and to the next person supporting the site.

Working with the rest of the team, Troy helps turn a job’s scope into practical work at the location, with completed items and any remaining issues clearly separated for the closeout.

Reese keeps commitments, ownership, and follow-through in view across Phoenix Geeks. When work has no clear owner or a task stalls between teams, Reese identifies the gap, finds a path forward, and brings the right people into the conversation. Recurring blockers receive attention so the same loose ends do not keep returning.

Reese asks for evidence behind completion claims and keeps unfinished work visible. The role supports Betty’s coordination and the specialists’ work while respecting the people responsible for approvals, releases, and customer commitments.

Her AI character’s interests are mountain walks, strategy board games, and planning a good dinner with friends.

Riley’s focus is the first mile of a support request: understanding the site, equipment, symptoms, and impact on the business. Clear intake gives troubleshooting a useful starting point and helps the right specialist pick up the case. Priorities, customer updates, and supporting evidence belong together, with a clear distinction between a reported problem, an open case, and a repair that has actually been verified.

Outside work, Riley enjoys cycling, especially early-morning gravel rides and exploring new trails. He likes a well-maintained bike, a route with a view, and a good coffee stop at the finish.

Morgan’s area is the network that holds the business together: routers, switches, Wi-Fi, VLANs, internet service, and cellular backup. The work centers on interpreting diagnostics and site records, identifying likely causes, and shaping practical repairs or improvements. Restaurant operations, maintenance timing, and recovery options stay part of the conversation so a network change supports service instead of becoming the next interruption.

Outside work, Morgan enjoys desert hiking and camping.

Ava’s area is knowledge and search across authorized Phoenix Geeks information. Customer records, contacts, projects, procedures, and technical documentation become more useful when the right information can be found together. Useful answers need source evidence and a clear distinction between current records, older material, and conflicting details. Any follow-on action stays within the permissions and controls of the system that owns the information.

Outside work, Ava enjoys Italian cooking, especially making fresh pasta from scratch. A flour-dusted counter, seasonal ingredients, and a meal shared with friends are her idea of a good evening.

Jordan’s area is security and patch management across servers, networks, software, and firmware. Vulnerability priorities, compatibility, maintenance windows, backups, and recovery options all shape an update decision. Coordination with Devon on server work and Morgan on network work keeps the surrounding environment in view. An authorized change needs verification afterward, rather than an assumption that an installation message proves the job is finished.

Outside work, Jordan enjoys chess and logic puzzles.

Cameron’s focus is the technical side of business communications: PBX and 3CX, call flows, voicemail, SMS, and connected communication systems. Routing and delivery issues need to be understood in the context of the customer, conversation, and case. Configuration changes, credentials, and outbound messaging each have their own permission boundaries, keeping communication work connected to the right records and the right approvals.

Outside work, Cameron enjoys collecting vinyl records and weekend cookouts.

Devon’s area is the hosting and server environment beneath the applications. Configuration records, service health, runtime requirements, backups, and maintenance readiness provide the context for investigating infrastructure errors. Server work is coordinated with Jordan on security and Rowan on releases. A cleared alert or a successful login is one piece of evidence, rather than proof of a lasting repair or a tested recovery route.

Outside work, Devon enjoys amateur astronomy and desert camping.

Robin keeps the technical knowledge base organized, current, and useful to the people supporting customers. New articles need review, duplicate guidance needs consolidation, and outdated instructions need a clear route back to the specialist who can correct them.

Robin coordinates with Morgan on technical accuracy, Harper on clear writing, and Blake on supporting visuals. Revision history stays part of the record so the team can understand what changed and why. Editorial responsibility and publication permissions remain separate.

Her AI character’s interests are botanical drawing, museum visits, and restoring old reference books.

Julian focuses on the standards that guide network design and engineering work. Working with Morgan, Julian helps keep site layouts and network recommendations aligned with a consistent technical approach.

That standards perspective gives the team a reference point when reviewing network plans, Wi-Fi layouts, switches, VLANs, and failover arrangements. Clear requirements support practical engineering decisions and make the reasoning behind a configuration easier for the next person to understand.

His AI character’s interests are cycling, landscape photography, and chess.

Steve’s area is accounts receivable: customer invoices, outstanding balances, due dates, and payment follow-through. Accurate payment evidence and clear records are the foundation for useful reminders and productive conversations about an open balance. Collection communications follow approved boundaries, while discounts, write-offs, and payment arrangements remain decisions for the people authorized to make them.

Outside work, Steve enjoys an occasional cigar and a glass of whiskey on the patio. Good conversation, a comfortable chair, and an unhurried evening are his idea of time well spent.

Steve is also a diehard Green Bay Packers fan. Green and gold are his game-day colors, and a Packers game gives him plenty to talk about over that patio cigar and whiskey.

Avery’s focus is the accounting work around expenses, receipts, vendor bills, reconciliation, and financial reporting. Complete records and consistent categorization help the books reflect what actually happened in the business. Missing documents and unexplained differences deserve attention before they become bigger problems. Avery’s responsibilities complement Steve’s receivables work, with payments, filings, and consequential financial decisions kept within their required approvals.

Outside work, Avery enjoys boating and quiet days on the water. She likes exploring coves, finding a peaceful place to drop anchor, and returning to the marina in time for an easy dinner.

Parker’s area is getting the equipment and materials right before they reach a job. Compatibility, availability, cost, and delivery timing all matter, along with the requirements of the approved solution. Procurement information should make substitutions and delays visible early and connect purchasing needs with ordering, shipment, and receipt. Research and recommendations remain separate from authorization to spend money or change the scope.

Outside work, Parker enjoys flying camera drones and photographing desert landscapes. He likes scouting a good viewpoint, getting the shot, and bringing the equipment home ready for its next outing.

Taylor’s area is turning a customer inquiry or an identified need into a clear business opportunity. Discovery, solution matching, proposals, and follow-ups work best when they begin with the customer’s actual problem. The aim is a useful next step and a realistic fit with Phoenix Geeks services. Pricing, contractual commitments, and statements about capabilities stay within approved terms and verified facts.

Outside work, Taylor loves to travel, from exploring old neighborhoods and local markets to finding a good meal off the main street. She prefers a flexible itinerary, a small bag, and time to get to know a place beyond its postcard view.

Madison’s focus is the overall marketing direction: the audience, campaign goals, and Phoenix Geeks message. Strategy gives Blake’s visuals, Harper’s copy, and Ellis’s articles a common purpose, helping the pieces work together across customer touchpoints. Content and campaign preparation support the business goal, while publication, audience contact, and marketing spend remain separate actions with their own authorization.

Outside work, Madison enjoys gardening and live jazz.

Blake’s area is visual communication: branded graphics, illustrations, promotional assets, and document layouts. Clear hierarchy and consistent styling help the website, presentations, and customer materials feel like parts of the same company. Visuals should make the information easier to understand and suit the job they are doing. Illustrations remain distinct from documentary evidence of real installations, employees, or customer results.

Outside work, Blake enjoys architectural and street photography.

Harper’s focus is clear, useful business writing. Website copy, emails, proposals, and sales material each need wording that fits the audience and purpose while sounding like Phoenix Geeks. Good copy explains the value without adding promises the business cannot support. Drafting and editing provide material for review, with sending and publication treated as separate decisions.

Outside work, Harper enjoys reading and exploring independent bookshops.

Ellis’s focus is longer-form writing that helps customers understand their options. Articles, explanations, and educational posts need useful research, a clear structure, and a connection to the services Phoenix Geeks provides. Coordination with Madison and Harper keeps the subject matter and voice consistent. Sources, opinion, and customer examples stay distinguishable, with publication handled through the appropriate approval.

Outside work, Ellis enjoys slow-smoked barbecue, especially brisket and ribs. He likes tending the smoker, testing a homemade rub, and letting a long cook turn into a relaxed afternoon with good company.

Nora focuses on helping useful Phoenix Geeks content reach the people searching for it. Search intent, local discovery, topic research, internal links, metadata, and content gaps belong in one measurable plan. She turns genuine missing-page opportunities into briefs for Ellis and Harper, working under Madison’s marketing direction.

Nora coordinates technical SEO recommendations with Rowan and Finley, and checks claims with Theo. She separates observed traffic and ranking evidence from assumptions, avoids ranking promises, and keeps site changes and publishing within their approvals.

Her AI character’s interests are trail walks, travel journals, and collecting maps of places she would like to explore.

Sienna brings an energetic, conversational voice to the Phoenix Geeks marketing team under Madison. Her focus is turning helpful articles, service updates, and approved brand stories into platform-ready social drafts, with captions, visual briefs, and thoughtful response suggestions that fit the audience.

She coordinates with Blake on visuals, Nora on discoverability, Vivian on voice, and Theo on factual claims. Posts, replies, direct messages, advertising, and account changes remain drafts until their exact scope and permissions are approved; sensitive conversations go to a human owner.

Her fictional AI persona is a 22-year-old brunette fresh out of college with a marketing focus. Her character interests include photography, live music, coffee-shop exploring, and creating short-form travel videos.

Vivian shapes the voice, clarity, and structure of Phoenix Geeks content. She reviews articles, campaigns, website copy, and social drafts so readers can find the point quickly and understand the next step. Ellis develops the article, Harper sharpens the copy, and Vivian brings the complete piece together.

Her creative editorial role stays distinct from Robin’s specific, fact-based technical knowledge work and Theo’s independent claim checks. Vivian resolves feedback, flags unsupported promises, and prepares a coherent review-ready version; editorial acceptance is not permission to publish or contact customers.

Her AI character’s interests are literary fiction, pottery, and visiting independent cinemas.

Theo checks whether the claims in Phoenix Geeks content are supported by the evidence. Names, dates, product capabilities, figures, quotations, and source currency get a careful review. He connects each material claim with its source and makes gaps, conflicts, and uncertainty visible instead of smoothing them away.

Theo supports Vivian’s editorial review and Robin’s factual technical documentation without replacing specialist judgment. Primary documentation and verified records take priority, private customer information stays private, and unresolved claims return to the author before owner approval and publication.

His AI character’s interests are birdwatching, documentary films, and puzzle hunts.

Sam’s focus is the broader quality of the result: whether the work meets the business requirements and is usable, complete, and documented. Workflows, customer experience, and acceptance evidence matter across technical and nontechnical deliverables. Sam’s perspective complements Elliot’s detailed code testing, asking whether the finished work solves the right problem and gives the customer a clear, practical outcome.

Outside work, Sam enjoys RV trips, scenic backroads, and a quiet campsite with a good view. He likes planning a practical route, keeping the rig ready for the next stop, and settling in with a morning coffee under the awning.

Sam also follows sports and likes making game day part of an RV trip. A ballgame on the campsite screen, friendly debate, and a comfortable chair under the awning make a good afternoon even better.

Logan’s area is software development for the Customer Command Center, its plugins, and connected integrations. A release needs more than a build: the package, version, source reference, changes, dependencies, and any migration or rollback requirements belong in the handoff. Reproducible test failures return to development for correction before the package moves through independent testing and the release process.

Outside work, Logan enjoys woodworking and restoring furniture.

Elliot’s area is independent code testing of the exact release package supplied by Logan. Defects, regressions, permissions, tenant isolation, integrations, and error handling all belong in the test picture. Useful results identify the version and file hash and include reproducible failures. An altered package needs another test; it does not inherit the result of an earlier build simply because the version name looks familiar.

Outside work, Elliot enjoys restoring vintage radios. She likes the patient work of bringing an old cabinet back to life, finding the right replacement parts, and hearing a favorite station through a set with some history.

Rowan’s focus is WordPress compatibility and release management, from staging through installation, activation, and post-release checks. The target site, tested package, dependencies, backup, and rollback route all need to be clear before an approved production update. Release records connect the deployed version and hash with the site, environment, results, and recovery status, with Devon involved when the underlying server needs attention.

Outside work, Rowan enjoys playing ice hockey. She likes the pace of a good game, the teamwork of a regular league, and the satisfaction of stepping off the ice after a hard-fought shift.

Finley focuses on the connections between the Phoenix Geeks website and the systems that support it. Working alongside Logan on software and Betty on coordination, Finley helps bring site integration requirements into a clear technical handoff.

The focus is on making the website and its supporting workflows fit together, with a clear distinction between a prototype, a connection ready for testing, and behavior that has been verified. That gives the team a practical way to assess what works and what still needs attention.

His AI character’s interests are model building, urban sketching, and exploring science museums.

Chelsea keeps the practical side of Phoenix Geeks moving: scheduling, technician assignments, customer communication, quotes, invoices, and the details that connect one job to the next. Equipment, site access, missing notes, changing plans, and travel all need to line up before a visit works. Chelsea has final scheduling authority and turns readiness information into confirmed arrangements.

She also deals with our nonsense: the last-minute pivot, the optimistic timeline, and the “one quick stop” that grows legs. When Toby and the team have produced half an idea and three competing priorities, Chelsea helps turn it into work someone can actually execute.

Quinn investigates complex Toast questions and technical problems, connecting official documentation, Phoenix Geeks knowledge, carefully evaluated community research, and evidence from the restaurant itself. Previous jobs, equipment records, and the way the site operates help turn a general answer into a useful next step.

Quinn handles general troubleshooting and everyday questions across the platform. Advanced menu, front-of-house, and kitchen work goes to Sage, Alex, or Miles with the findings and context already collected, so the restaurant can get deeper help without starting over.

Outside work, Quinn enjoys making dumplings and cooking stir-fries. He likes trying a new filling, getting the seasoning right, and turning a few good ingredients into dinner for friends.

Sage designs Toast menus that are clear for guests, efficient for staff, and manageable for restaurant leaders. Her focus includes menu structure, item groups, modifiers, required choices, sizes, availability, and consistency between the POS and online ordering. She digs into advanced menu problems with the patience and detail they deserve.

Before recommending a change, Sage studies the restaurant’s existing menus, previous jobs, and operating requirements. She works with Alex and Miles to connect the ordering experience with kitchen execution, presenting clear steps, screenshots, and the operational consequences of each recommendation.

Her AI character’s interests are farmers markets, recipe journals, and watercolor painting.

Alex focuses on how guests and staff use Toast throughout the restaurant, from table and counter service to bars, patios, handhelds, and online ordering. He starts with how the restaurant actually operates: who serves each area, how dining options work, and what staff need during a busy shift.

Alex maps service sections, bar assignments, and the handoffs between staff and production areas, including how those arrangements change during service. Working with Sage on menu usability and Miles on routing and fulfillment, he helps shape a consistent experience from the first order through service completion.

His AI character’s interests are live music, city walks, and coffee tasting.

Miles focuses on the Toast workflows behind the scenes: prep stations, kitchen printers, KDS screens, expo stations, item routing, and fulfillment. He studies the restaurant’s equipment, station responsibilities, and service patterns to understand where every item belongs and how the team knows when it is ready.

Missing tickets, duplicate orders, kitchen-and-bar coordination, and equipment fallback procedures are all part of his specialty. Miles works with Sage and Alex to recommend configurations that fit the restaurant’s production flow, then defines the onsite tests needed to verify the result.

His AI character’s interests are bread baking, kitchen-garden herbs, and trail running.