Existing customer support

Support

Request help with an existing WMT product, service, implementation, environment, or operational issue.

Prepare the request

Useful context helps WMT respond more effectively.

WMT uses the organization, product, operational impact, and reproduction context to route and prioritize the request.

OrganizationSector, location, size, campuses or sites, and responsible team.
Current environmentExisting systems, data, users, workflows, integrations, and constraints.
Desired outcomeWhat should improve, when it matters, and how success will be evaluated.

Secure request

Support

Fields marked with an asterisk are required.

Please do not include passwords, credentials, sensitive personal data, or confidential records.

Include screen, module, steps, timing, users affected, error text, recent changes, and safe reproduction details. Do not submit passwords or sensitive records.

Provide a non-sensitive environment name or public URL only.

Information is handled according to the Privacy Policy. Form processing, spam protection, routing, and retention must be connected to the approved production platform before launch.

Questions

Frequently asked questions

What information makes a support request useful?

Include organization, product, module, environment, affected users, timing, business impact, expected behavior, actual behavior, steps, error text, and recent changes.

How should urgent issues be reported?

Use the emergency or priority channel defined in the customer support agreement and state the actual operational impact, affected scope, and safe contact details.

Should I send screenshots or data files?

Only through an approved secure channel and only after removing unnecessary personal, confidential, or credential information.

Can support requests include enhancement ideas?

Yes, but incidents, questions, configuration requests, and enhancements follow different assessment and release processes.

Where can a customer access its application?

Use the Client Login page or the customer-specific URL provided during implementation. Access questions should identify the organization without sharing credentials.