EffingTech client support

Support that starts with a real person.

Report a website issue, request a change, ask for help with an EffingTech application, or continue an existing conversation through one trackable support ticket.

Submit a Support Request Email Support
Website and application supportTicket status and historyEmail replies stay connected
EffingTech SupportJira connected

Customer requests

Help Desk

Secure ticket workflow
Website unavailableCritical website or hosting issue
New
Content update requestedText, image, or page revision
In progress
Contact form repairedCustomer reply and resolution history
Resolved
Ticket prefix ETSPowered by Jira Service Management
One request, one conversationReplies remain attached to the same ticket.
Customer-visible statusSign in to review requests and updates.
Built for current clientsCrossroads and future EffingTech customers.

Get help

Choose the support path that fits the issue.

The EffingTech request form is best for detailed requests. Jira remains available behind the scenes for ticket history, status, and email replies.

Submit a request

Create a new support ticket without leaving the EffingTech experience. Add the issue details, urgency, affected URL, and an optional screenshot or file.

Open Request Form Stays on EffingTech.com; Jira handles the ticket securely behind the scenes.

View my requests

Sign in to the support website, open My requests, and review ticket status, replies, and previous conversations.

Open request history ↗

Email support

Send a message directly to the help desk. Your subject becomes the ticket summary and the message becomes the request description.

support@effingtech.atlassian.net →

Remote assistance

Already working with EffingTech on an issue? Join an attended Zoho Assist session after you receive a Session ID from us.

Join Remote Session Remote access starts only after you join the session and approve the connection.

Website down or seriously broken?

Mark the request urgent and tell us exactly what is failing.

Urgent reports should be reserved for public outages, broken customer-facing forms, domain or certificate failures, or another problem that stops normal business use.

Report an Urgent Issue Send urgent email
01
Affected addressInclude the exact website URL, page, form, or application screen.
02
What you seeDescribe the message or behavior and attach a screenshot when possible.
03
Who is affectedTell us whether the problem affects everyone, one location, or one device.
04
When it beganShare the approximate time and whether anything changed immediately beforehand.

What happens next

A straightforward support workflow.

The portal and email channel feed the same EffingTech support queue, keeping the request, replies, status changes, and resolution together.

01 · SUBMIT

Describe the request

Use the support website or send an email with enough context to understand the issue.

02 · TRACK

Receive an ETS ticket

The request receives a ticket number and a confirmation email for future replies.

03 · DISCUSS

Reply in either place

Continue through email or the customer support website without starting a new conversation.

04 · RESOLVE

Keep the history

Status changes, public replies, and the final resolution remain attached to the request.

Common request types

Support for the things EffingTech builds and maintains.

Website unavailable

Hosting, page-load, DNS, domain, or certificate failures.

Page or feature error

Broken navigation, layout, links, scripts, or expected behavior.

Form or email problem

Submissions, notifications, routing, or customer-contact issues.

Content update

Text, images, documents, staff, locations, hours, or announcements.

Domain, DNS, or SSL

Address changes, records, redirects, certificates, and renewals.

Performance problem

Slow pages, large assets, browser issues, or device-specific behavior.

Application support

Questions or problems involving an EffingTech Windows application.

General question

Anything that does not fit cleanly into another support category.

Response expectations

Priority follows business impact.

Requests are reviewed during EffingTech’s normal working availability. Urgent outages receive priority, while planned changes are scheduled around active work and the customer’s support arrangement.

UrgentA public website, form, domain, or essential service is unavailable.
NormalA feature is broken, confusing, or needs technical investigation.
PlannedA content update, enhancement, or non-urgent improvement is requested.

Protect your information

Do not place passwords in a support ticket.

Tickets are designed for issue details, screenshots, and ordinary project information—not credentials or sensitive personal data.

  • Never send or disclose passwords, recovery codes, or payment-card details.
  • Remove private customer information from screenshots when possible.
  • Only join a remote session after receiving a Session ID directly from EffingTech.
  • Remote access is attended and begins only after you approve the connection.
  • Include only the minimum information needed to explain the issue.

Ready to open a support request?

Use the customer support website for the best tracking experience, or send an email when that is more convenient.

Submit a Request Email Support