Lead Repository

Follow-up planned to acknowledge the recent provider change and keep in touch.

Follow-up planned to confirm the annual contact preference.

Follow-up planned to send the calendar invitation and confirm attendees.

Follow-up planned to offer specific times next week and send a calendar invitation.

Follow-up planned to outline available AI and automation services alongside managed IT.

Follow-up planned for the middle of next week to lock in a time.

Follow-up planned with the IT owner to introduce co-managed support options.

Follow-up planned to introduce services to the business systems manager without pressure.

Follow-up planned to acknowledge the annual contact preference.

Follow-up planned to confirm the annual contact preference.

Follow-up planned to send the Zoom invitation for the agreed slot.

Follow-up planned to confirm the proposed time and send an invitation that works across time zones.

Follow-up planned to confirm the time and send a calendar invitation.

Follow-up planned to confirm an in-person visit to the practice.

Follow-up planned to confirm the call and prepare answers on legal-specific applications.

Follow-up planned to confirm Sage 100 Advanced support and current team contacts.

Follow-up planned to confirm meeting logistics and gather RFP requirements.

Follow-up planned to send the meeting invitation to all three attendees.

Follow-up planned to outline Sage 100 support experience.

Follow-up planned to confirm on-site partnership options and request an introduction.

Follow-up planned for next week to set a time.

Follow-up planned with the owner to introduce managed IT services.

Follow-up planned with the COO to introduce services without pressure.

Follow-up planned with the IT team to introduce services.

Follow-up planned with the IT contact to introduce services.

Follow-up planned to confirm the summer 2027 timeline.

Follow-up planned to note the renewal timeline.

Follow-up planned to acknowledge the convention and reconnect afterward.

Follow-up planned to coordinate with the team already engaged on the project.

Follow-up planned to scope the Google migration and iPad rollout.

Follow-up planned to stay in touch without pressure.

Follow-up planned to acknowledge the contract and busy season.

Follow-up planned to acknowledge the annual update preference.

Follow-up planned with the colleague to lock in a time next week.

Follow-up planned to offer slots next week.

Follow-up planned with the IT lead to introduce services.

Follow-up planned with the IT director to introduce co-managed support.

Follow-up planned for early December, once the owner is back.

Follow-up planned with the IT director to introduce co-managed support.

Follow-up planned to acknowledge the current provider.

Follow-up planned to confirm the check-in cadence.

Follow-up planned to confirm the July 2027 timeline.

Follow-up planned to confirm the annual update.

Follow-up planned to send the Teams invite to the updated email.

Follow-up planned to confirm the call and send an invitation.

Follow-up planned to share an indicative on-call pricing range.

Follow-up planned to confirm requirements and set a meeting.

Follow-up planned to confirm the time and send an invitation.

Follow-up planned to confirm the time and send an invitation.

Follow-up planned with the owner to propose call times.

Follow-up planned for after November 16.

Follow-up planned to note the timeline.

Follow-up planned to stay in touch without pressure.

Follow-up planned to note the renewal.

Follow-up planned to note the timeline.

Follow-up planned to share service details and pricing.

Follow-up planned to confirm the meeting details.

Follow-up planned to share availability for next week.

Follow-up planned to share service details.

Follow-up planned to send the service offerings.

Follow-up planned to stay in touch without pressure.

Follow-up planned to note the timeline.

Follow-up planned to stay in touch without pressure.

Follow-up planned to note the contract timeline.

Proposed a short call with the IT department to understand current coverage and identify any support gaps.

Proposed a brief introductory call once the right IT decision-maker has been identified.

Proposed a short call with the IT manager at a time that works around the team's current workload.

Proposed an introductory call to review the firm's current IT setup and support needs.

Proposed using the repair as an introduction to ongoing support for the company's laptops and users.

Future check-in proposed for February 2027 to see whether more hands-on local support has become relevant.

Future check-in proposed for January 2027 to share an overview of available IT services.

Future check-in proposed for January 2027 to revisit the company's IT requirements.

Future check-in proposed for September 2027 to review any changes in the practice's IT requirements.

Future check-in proposed for September 2027 to see whether IT support has become a priority.

Proposed walking through the audit approach and reporting deliverables on a call with the firm's partner.

Proposed gathering details on current systems and support pain points before the call so a quote can be prepared.

Proposed sending a reminder and short agenda ahead of the January discussion.

Proposed presenting a cost comparison against the current provider once requirements are gathered.

Proposed a short agenda covering the university's current IT setup and how an outsourced model would support it.

Proposed reviewing where co-managed support could back up the internal IT manager across users and plant systems.

Proposed gathering details on the outgoing provider's scope so a transition plan can be discussed on the call.

Future check-in proposed for April 2027 to see whether local IT decisions have shifted.

Future check-in proposed for January 2027 to book the short introductory call.

Proposed preparing dealership-relevant examples of IT support ahead of the call.

Proposed a short review of the firm's current IT setup and support needs.

Proposed a call to walk through CMMC readiness and the support needed for a self-audit.

Proposed an introductory call with the team members who would support the account.

Proposed a short call with the executive director to compare support against the current vendor.

Future check-in proposed for August 2027 to see how the new provider is performing.

Future check-in proposed for September 2027 to review tech support needs.

Proposed an agenda covering where co-managed support could extend the internal IT team across sites.

Proposed reviewing how co-managed support could cover the franchise network's IT needs.

Proposed a short call to understand the AI use cases the company is exploring.

Proposed a short agenda on the authority's current IT support arrangement.

Proposed a brief call to understand the shop's systems and support gaps.

Future check-in proposed to share relevant updates and offerings.

Future check-in proposed for October 2027 to review IT support needs.

Future check-in proposed for October 2027 to share updates on IT services.

Proposed covering the company's current IT setup across trucking, warehousing and office systems.

Proposed an overview of how local support would work alongside the German head office.