Spaces:
Sleeping
Sleeping
| """ | |
| Tools by team reference. Internal audience only. Each team lists the systems it | |
| already uses and where Claude Enterprise fits next to them. | |
| Note on connectors: unless BOS IT has set up a connector for your team, assume | |
| Claude does not reach into Zoho, Apollo, or Microsoft 365 on its own. You copy | |
| material in, work on it, and paste results back out. Ask IT what is connected. | |
| """ | |
| TEAMS_INTRO = """ | |
| <p>Every team at BOS works out of the same three platforms: Zoho for CRM, helpdesk, | |
| and workflow, Apollo for prospecting data and outreach, and Microsoft 365 for | |
| email, Teams, and files. Claude Enterprise sits alongside them as the drafting and | |
| thinking layer. This page shows, team by team, where it fits and what stays out.</p> | |
| <p><b>A note on connections.</b> Unless BOS IT has set up a connector for your team, | |
| assume Claude does not reach into Zoho, Apollo, or Microsoft 365 on its own. You | |
| copy material in, work on it, and paste the result back where it belongs. If a | |
| connector is available to you, IT will have told you what it can see and what | |
| rules apply. When in doubt, ask.</p> | |
| """ | |
| TEAMS = [ | |
| { | |
| "name": "BOS Staffing", | |
| "html": """ | |
| <h3>What you already use</h3> | |
| <p><b>Zoho.</b> Candidate and client records, tasks, and workflow. | |
| <b>Microsoft 365.</b> Outlook for client and candidate email, Teams for the internal | |
| back and forth, SharePoint and OneDrive for documents and templates. | |
| <b>Internal job posting tool.</b> The BOS generator for formatted job postings, built | |
| and maintained by IT.</p> | |
| <h3>Where Claude fits</h3> | |
| <p><b>Job postings.</b> Start from the internal posting tool, then use Claude to | |
| adjust tone for a specific market or to write three subject line options for the | |
| distribution email. Give it the role, the shift pattern, and the location. Do not | |
| give it a candidate.</p> | |
| <p><b>Client communication.</b> Paste your rough notes from a client call and ask for | |
| a clean follow up in your voice. Refer to the client generically in the draft and | |
| fill the name in afterward in Outlook.</p> | |
| <p><b>Interview structure.</b> Ask for a competency based question set for a role | |
| type, then adapt it. This produces the framework, not a judgment about any person.</p> | |
| <p><b>Process writing.</b> Turning how you actually do a placement into a written | |
| procedure a new coordinator can follow.</p> | |
| <h3>What stays out</h3> | |
| <p>Individual resumes, applications, background or drug screening results, | |
| compensation, disciplinary notes, and anything from a personnel file. Any | |
| AI assisted resume screening happens only through the workflow IT and HR have | |
| approved, not through a chat window. If you are not sure whether that workflow | |
| exists yet, ask BOS IT before you paste a single resume.</p> | |
| """, | |
| }, | |
| { | |
| "name": "BOS Security", | |
| "html": """ | |
| <h3>What you already use</h3> | |
| <p><b>Zoho.</b> Client accounts and the helpdesk queue. | |
| <b>Microsoft 365.</b> Outlook for client and officer communication, Teams for shift | |
| coordination, SharePoint for post orders, schedules, and quality check records.</p> | |
| <h3>Where Claude fits</h3> | |
| <p><b>Post orders and procedures.</b> Paste an existing post order and ask for a | |
| version a brand new officer can follow on night one. Keep the site referred to as | |
| the site, and keep gate codes, alarm codes, and contact numbers out of the chat.</p> | |
| <p><b>Client updates.</b> Turn a week of scheduling notes into a plain language | |
| summary at the metric level: fills, coverage percentage, open shifts. Not which | |
| guard was late at which site.</p> | |
| <p><b>Training material.</b> Explaining a policy, a uniform standard, or a de-escalation | |
| principle in language that lands with the officers who read it.</p> | |
| <p><b>Trend analysis.</b> Describe the pattern you are seeing in incident counts by | |
| type and month, without the narratives, and ask what questions a client would ask | |
| about it.</p> | |
| <h3>What stays out</h3> | |
| <p>Incident narratives, dispatch records, law enforcement interaction details, | |
| officer personnel and pay information, client site access details, and anything | |
| tying a specific incident to a specific site in material that could leave the | |
| company.</p> | |
| """, | |
| }, | |
| { | |
| "name": "Sales", | |
| "html": """ | |
| <h3>What you already use</h3> | |
| <p><b>Zoho CRM.</b> Pipeline, accounts, contacts, the integrator and channel partner | |
| database, and the new site approval workflow. | |
| <b>Apollo.</b> Prospect data, contact lists, and outreach sequences. Lead exports from | |
| internal tools land here in the VirtuGuard Apollo template. | |
| <b>Microsoft 365.</b> Outlook, Teams, and shared proposal files. | |
| <b>Internal sales apps.</b> The VirtuGuard pricing calculator and the camera and VMS | |
| compatibility lookup, both maintained by IT.</p> | |
| <h3>Where Claude fits</h3> | |
| <p><b>Outreach drafts.</b> Pull the prospect's company name and industry from Apollo, | |
| give Claude the trigger event and the two differentiators that matter for that | |
| vertical, and ask for a short first touch in your voice. Then edit. Sequences | |
| still get built and sent from Apollo.</p> | |
| <p><b>Call prep and recap.</b> Paste your notes after a discovery call and ask for a | |
| follow up email plus a list of open questions. Log the recap in Zoho yourself.</p> | |
| <p><b>Explaining the service.</b> Ask for a plain language explanation of remote video | |
| monitoring for a property manager or general contractor who has never used it. | |
| Strip the jargon, keep it honest about what a camera can and cannot see.</p> | |
| <p><b>Proposal sections.</b> Draft the narrative sections. Pricing comes from the | |
| pricing calculator, never from the AI. Compatibility comes from the lookup tool | |
| and the Immix integration matrix, never from the AI.</p> | |
| <h3>What stays out</h3> | |
| <p>Contract values and client names in anything that could be forwarded, camera | |
| locations and site addresses in external material, and any claim about | |
| certifications, insurance, licensing, guaranteed response times, or regulatory | |
| compliance that you do not have a source document for. Never let Claude fill in | |
| a price or a compatibility answer.</p> | |
| """, | |
| }, | |
| { | |
| "name": "VirtuGuard", | |
| "html": """ | |
| <h3>What you already use</h3> | |
| <p><b>Immix.</b> The monitoring platform where alarms, patrols, and site details live. | |
| <b>Camect and camera analytics.</b> Edge detection and filtering at the site. | |
| <b>Zoho Desk.</b> Knowledge base for VMS sheets and SOPs, plus the helpdesk queue. | |
| <b>Microsoft 365.</b> Outlook for end of shift reports and outage notices, Teams for | |
| real time escalation, SharePoint for KPI workbooks and incident documents. | |
| <b>TalentLMS.</b> Monthly assigned agent training.</p> | |
| <h3>Where Claude fits</h3> | |
| <p><b>Shift reports and notices.</b> Standardize the format of an end of shift report or | |
| an outage notification without changing the facts. Refer to the site generically in | |
| the chat, then fill it in when you paste back to Outlook.</p> | |
| <p><b>SOPs and VMS sheets.</b> Paste a rough procedure and ask for a step by step version | |
| a new agent can follow. Publish it in Zoho Desk. Credentials, IPs, and port details | |
| never go into the chat.</p> | |
| <p><b>Understanding the technology.</b> Explaining what a detection module does, why a | |
| camera over alarms in wind or rain, what a voice down is meant to accomplish, or how | |
| edge analytics reduce noise. Good for onboarding and for the weekly tech briefing.</p> | |
| <p><b>KPI narrative.</b> Give it the numbers from the KPI workbook, response times, | |
| alarm counts, patrol compliance, and ask for the two paragraph narrative that goes | |
| with the charts.</p> | |
| <h3>What stays out</h3> | |
| <p>Video descriptions, incident narratives, dispatch and law enforcement details, | |
| site network configurations, NVR and VMS logins, camera locations, and the | |
| staffing ratio figures leadership has asked to keep internal.</p> | |
| """, | |
| }, | |
| ] | |