AVERANE / CLIENT SUPPORT
Your next change.
Your next question.
Start here.
You know your business.
You do not have to diagnose your website.
Tell us what you need, what you are seeing, and what it affects. A little context helps turn a question into a clear, reviewable request.
PREPARE A SUPPORT REQUEST THE REQUEST BEHIND THE REQUESTSomethingisn’t working.
Start with what you expected, what happened, and the steps that led there.
CONTEXT → CLARITY → NEXT STEPCare beginswith understanding.An issueAn updateAn idea
Explore the guidance, then prepare your request below. This illustration does not submit a ticket.
AVERANE / CLIENT SUPPORT
Keep your website
moving forward.
A question, a change, or something that needs attention? Give us the context behind it. Clear details help turn a support request into a useful next step.
From content updates to technical issues, start with what you are trying to do, what is happening, and how it affects your business.
Prepare your support ticketGOOD SUPPORT STARTS WITH UNDERSTANDING
Your context matters.
- 01The experience.The page, feature, or task involved.
- 02The impact.Who is affected and what they cannot do.
- 03The intended result.What needs to change or work differently.
MAKE THE FIRST MESSAGE USEFUL
The detail that helps us
understand the whole picture.
Point to the experience.
Include the affected page address and explain which part of the website you mean. If the issue appears only on a particular device or browser, include that context too.
Describe the difference.
Explain what you expected and what actually happened. For a planned update, describe the intended result and identify the approved material or relevant pages.
Explain why it matters.
Tell us who is affected and which activity is blocked. Include a relevant deadline and why it matters, so priorities can be discussed against the support arrangement.
BEFORE YOU PREPARE THE REQUEST
A clearer handoff.
Fewer missing pieces.
You do not need a technical explanation of the cause. Useful observations and approved content give the work a better starting point.
Reporting unexpected behaviorShare a repeatable sequence: where you started, what you selected, and what happened next. Note when you first noticed the issue and whether other people see it. Quote relevant error text without including private information.
Requesting a content changeIdentify the page and the exact content to replace. Prepare final copy, suitable image assets, and any related links. Explain whether the update also applies elsewhere on the website.
Exploring new functionalityDescribe what someone should be able to do and why. Mention connected tools or workflows. Feasibility, scope, dependencies, and acceptance criteria need review before work is agreed.
Handling sensitive informationDo not include passwords, payment details, private customer records, or sensitive personal information in the request. Access and confidential material should use an agreed secure process.
LET’S GET THE DETAILS TOGETHER
What needs
our attention?
Choose the closest topic. The guidance and your prepared ticket will update together.
Website issueContent updateAccess helpHosting or performanceNew requestTell us what happened.
Include the affected page, the expected result, the actual result, and steps that reproduce the issue.
Outage or suspected security incident?
Use the urgent reporting route in your support agreement. For urgent incidents, follow the escalation instructions in your agreement rather than waiting for a form response.
Not an existing client? Book a consultation to discuss your needs.
Create a support ticket.
Send your request to Averane.Complete the required fields and select Submit Ticket. Wait for your confirmation and request reference before leaving this page. For follow-up, contact sayhi@weareaverane.com.
Your detailsName *Email *Company or organization *Your requestShort subject *TopicWebsite issueContent updateAccess helpHosting or performanceNew requestBusiness impactQuestion or planned improvementSome users or a feature affectedKey business task blockedWebsite unavailable / security concernAffected page or featureRemove private links, tokens, and sensitive query parameters.Details *Do not include passwords, authentication codes, payment details, patient information, or confidential records.Timing or deadlineRequested timing is context, not a confirmed completion commitment.Review your prepared ticketCopyable summarySUBMIT TICKETCOPY TICKET DETAILSA CLEAR PATH THROUGH THE WORK
Context. Alignment.
A considered resolution.
Define the request.
Share a specific example and business impact. Useful evidence helps establish what needs attention and what remains unclear.
Clarify the approach.
Scope, permissions, dependencies, and approvals may need discussion before work begins. Work outside the agreement is reviewed separately.
Validate the result.
Relevant checks and your feedback help confirm the intended change. Keep follow-up observations in the original request.
SUPPORT WITH CLEAR EXPECTATIONS
Before you send.
How do I submit a ticket?
Complete the support form and select Submit Ticket. Your request is received only when a confirmation and reference appear. You can also reach Averane at sayhi@weareaverane.com.
What if my website is unavailable?
Use the urgent contact route in your support agreement. Record the affected URL, exact error, and approximate start time. For urgent incidents, use the escalation route in your support agreement.
How quickly will I hear back?
Response times, service hours, and escalation arrangements depend on your support agreement. Describing the business impact helps the team assess the request.
Are all changes included?
Coverage depends on the agreed scope. New features, substantial design changes, integrations, and other work outside your plan may require a separate estimate and approval.
Can I include passwords or private records?
No. Never include credentials, payment details, patient information, or confidential records. Use an approved secure process if access or sensitive information is required.
What happens after a request is received?
The team reviews the context, clarifies requirements, and discusses the appropriate next step. Scope, dependencies, approvals, and testing requirements influence how the work proceeds.
Support topics and helpful context
Website issue
Tell us what happened.
Include the affected page, the expected result, the actual result, and steps that reproduce the issue.
Content update
Make the change clear.
Identify the page, approved replacement content, publishing deadline, and approval owner.
Access help
Help us identify the access problem.
Name the service and action you cannot complete. Never include passwords, recovery codes, or private keys.
Hosting or performance
Describe the affected experience.
Include the URL, approximate start time, browser/device, and whether the behavior is consistent.
New request
Start with the outcome.
Describe who needs the change, what it should accomplish, relevant dependencies, and timing.
Something isn’t working.
Start with what you expected, what happened, and the steps that led there.
Time for something new.
Identify the page, prepare approved content, and explain the intended change.
What if we could do more?
Describe what someone should be able to do and the outcome you want to make possible.