Someone close to the problem
Include the person who sees the interruption, risk, stalled work, or desired change clearly enough to explain its effect.
Make the first conversation useful.
Register or sign in through the EZ Support Portal, then bring the pressure, timing, and context you already know to the scheduling request.
The first conversation is for understanding the situation and deciding whether another step would be useful. Describe the problem or desired change, the people or systems affected, why the timing matters, and where responsibility is unclear. The portal keeps the request, scheduling context, and later service activity connected to the same private customer account.
You do not need a completed technical plan. Do not send passwords, authentication codes, private keys, payment-card information, detailed employee or customer records, or sensitive security evidence through ordinary email. Start with a non-sensitive summary so an appropriate way to exchange further detail can be agreed if needed.
Register, then choose a time
New customers start in the EZ Support Portal. Register or sign in, add a non-sensitive summary of the situation, and use the available scheduling path to request a consultation.
A requested time is not confirmed until the portal shows it as accepted. Availability and the participants required depend on the situation.
Open the EZ Support PortalWho should participate
Bring the people who can explain the situation and make the next decision. A full technical team is not required for an initial conversation.
The accountable decision-maker
When scope, priorities, budget, or business risk may be discussed, include the person responsible for those decisions or identify when they should join.
Technical context when useful
An internal technical lead or current provider can help when dependencies matter, but their participation can be decided after the situation is understood.
What the first conversation may clarify
The goal is a better-defined decision, not a promise that every detail will be resolved immediately.
Understand the situation
Discuss the pressure, affected people or systems, existing responsibilities, constraints, and why the decision matters now.
Identify missing context
Clarify which information, people, systems, or safeguards would be needed before a responsible recommendation or scope can be prepared.
Decide whether to continue
A possible next step may be a focused request, assessment, quote, project discussion, or managed-service conversation. Any purchase or service commitment requires affirmative portal acceptance or the applicable signed document.
What remains undecided
An initial conversation does not guarantee fit or establish scope, price, availability, response expectations, responsibilities, a start date, or a service commitment. Those details remain under review until they are explicitly confirmed in the appropriate written documents.