Submit a request
Create a new support ticket with a clear subject, description, affected website or application, and any helpful screenshots.
Open Request Form Opens the secure EffingTech request form hosted by Atlassian.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.
Website and application supportTicket status and historyEmail replies stay connected
EffingTech SupportJira connectedCustomer requests
Help Desk
Website unavailableCritical website or hosting issue
NewContent update requestedText, image, or page revision
In progressContact form repairedCustomer reply and resolution history
ResolvedOne 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 support website is best for detailed requests and tracking. Email remains available when you need to report something quickly.
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 →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.
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.
Describe the request
Use the support website or send an email with enough context to understand the issue.
Receive an ETS ticket
The request receives a ticket number and a confirmation email for future replies.
Reply in either place
Continue through email or the customer support website without starting a new conversation.
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 passwords, recovery codes, or payment-card details.
- Remove private customer information from screenshots when possible.
- EffingTech will arrange a safer method if secure access is required.
- 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.