Connects phone activity, Microsoft 365-style inbox/calendar, NetSuite-like customer records, dispatch constraints, and AR follow-ups.

Customer workspace
Isseks Operations
Ask Oscar
Coordinate calls, jobs, scheduling, records, and follow-ups
Daily operating brief with queue priorities, source gaps, and customer-safe draft actions.
Production path
47%NetSuite, Microsoft 365, SharePoint, telephony, scheduling, and AR graduate one connector at a time.
Today
Operating queue
Site history, access notes, crew timing, service window, and customer callback context.
Statement history, promise-to-pay notes, NetSuite-like invoice context, and email draft assembled.
Compares NetSuite-like records, email signatures, and call notes.
Systems
Connections Oscar needs for production
Read customers · Read jobs · Read invoices
NetSuite sandbox role and read-only credentials pendingRead shared inbox · Read calendar · Read SharePoint documents
Tenant admin consent pendingCall log read · Voicemail transcription
Phone provider discovery requiredRead documents
No current blockerCSV/Excel upload · Chart generation · PDF read
No current blockerEnablement
What Isseks still needs to provide
Confirm whether the production surface should say Isseks, Izzix, Zix, or another legal/brand name.
Provide sandbox/account details, read-only role, auth method, and sample records for parity testing.
Identify the provider and share API/webhook documentation or admin access path.
Confirm whether scheduling lives in NetSuite, Microsoft 365, another tool, or a manual process.
Name the tenant admin and confirm shared mailboxes, calendars, and SharePoint sites in scope.
Provide names, emails, roles, and whether SSO is required for launch.
Define approvers, evidence requirements, and which actions remain read-only.
Runbooks
Scenario studio
Coordinate calls, service jobs, scheduling exceptions, AR follow-ups, and customer reminders.
Output