Tervuq Navigation
Contact / Austin, Texas

Discuss a website or support request.

Contact Tervuq for business website development or website technical support in Austin. Describe the task you need a new interface to handle. For an existing site, send the page address and tell us what stopped working.

Discuss a request

Scope-based estimate in USD after inquiry. The work and access arrangements are agreed before work begins; submitting this form does not place an order.

TervuqRequest route / No checkout
Inquiry / Project or support

Website development or technical support?

Name and permission to handle the request are required. Add either a phone number or an email address so Tervuq can reply. You do not have to provide both.

Reply details

One reply route is required: phone or email. Each is optional on its own. If you add both, mention a preferred route in your message.

Leave this blank unless the address is relevant to the request. A postal address is not needed for a software inquiry.

The work or problem

Choose the nearest description. It routes the discussion; it does not commit you to a service.

For new work, describe the intended user and their task. For a fault, add a safe page address, what you did and what you saw. A requested deadline can be included for discussion, not as an agreed schedule.

Review this field before sending. You can paste a transfer calculation here, edit a carried summary, or remove it. Include the inputs and their units, not just a GB result.

Keep private records out of the form. Remove customer names and identifying details from examples. Do not paste diagnostic logs, signed access links or the contents of an account recovery email.

No payment is taken. An inquiry is not an order.

04 / Enough detail to start

Describe a task, not a technology wish list.

A clear first message is enough to open the discussion. You do not have to settle the architecture before contacting a digital studio.

These are illustrative prompts, not examples of delivered Tervuq projects. Use ordinary language and leave the unknowns visible.

For a website or rebuild

Say what the site needs to explain and who will edit it. If a website already exists, give its public address and identify the part that needs replacing. Mention an existing enquiry route that must keep working.

Example wording

“We need a public service website. Our current pages are difficult to update, and enquiries go to a shared inbox. We want to keep that reply route.”

Do not assume a rebuild requires replacing every connected service. The business website development outline explains how content and editing boundaries affect scope.

For website troubleshooting

Include the browser and device you used, the action that failed and the text of any error, with identifying details removed. Say whether it happens every time. If the fault began after a known change, mention the change without guessing its cause.

Example wording

“On a phone, the contact form returns to the top after Send. I cannot see a confirmation. It happened twice in the same browser.”

Do not submit a live customer request simply to test a fault. The website technical support page sets out the reproduction approach and the distinction between faults and changes.

For a signed-in workflow

Describe the roles in plain words. “Customers see their own documents; staff approve a document before it is shared” identifies a boundary. “We need a dashboard” leaves the important question unanswered.

Use invented labels such as Customer A in your own description, not real account details. Refer to customer portal development when the work centers on access to records. Use the internal tools outline when staff need a better queue or task interface.

For a planned maintenance request

Separate what is broken from what you would like to change. A new field may be easy to draw but affect exports or validation elsewhere. Say which existing behavior must remain unchanged.

For website maintenance in Austin, use this inquiry route. Include any dependency on a planned release or an outside provider. Dates are discussed as constraints; entering one does not establish a delivery promise.

05 / After sending

A receipt is not an agreement to work.

Request handlingScope before commitment

The form records an inquiry. A technical discussion and a written scope come before any project commitment.

Read the inquiry-to-handover process
01

Check the submission result.

A confirmed submission displays a receipt. If there is a field error, correct the named field. If the connection fails or the result is unclear, do not assume the inquiry was stored or repeatedly send it. Use a direct contact route and explain what happened.

02

Resolve the open questions.

The next discussion establishes which work is being requested and what is needed to assess it. A fault may need safe reproduction; a build may need a boundary around content or permissions. No opening hours or response-time commitment is implied by the form.

03

Agree the work separately.

Estimates are scope-based in USD after inquiry. A support investigation is agreed as an investigation, not a promise to resolve every related issue. Written acceptance criteria and any correction obligations belong in the work agreement.

06 / Other routes

Use the channel that fits the request.

There is no need to send the same description through the form and support chat. Keep a single thread where possible, or mention the existing receipt when following up.

A short support conversation

The Support control opens an asynchronous conversation. It is not a claim that an agent is online. Messages appear when available. Leave out passwords and private records there too.

A privacy or accessibility request

For access to, correction of or deletion of personal information, use the data request route or email office@tervuq.com. Do not send identity documents with a first message.

If a control or reading order prevents you from using this page, the accessibility statement explains how to report the barrier. Direct email and phone remain alternatives to this form.

A calculation to discuss

The website transfer calculator produces a page-transfer estimate, not an infrastructure recommendation. Paste its summary into the visible specification field and state how you measured the page weight. Check carried values before sending.

Data handling / Inquiry onlyRead before sending

Your submitted fields and consent tick become an inquiry record. The form also records request information such as the IP address, browser user-agent, referring URL and submission timing. Enquiries and their email copies are retained for 24 months.

Read the privacy statement

Google Ads, Microsoft Advertising and Meta Ads send visitors here. Their click identifiers are gclid, msclkid and fbclid respectively. The inquiry checkbox does not allow advertising storage. Consent Mode v2 keeps ad_storage, ad_user_data, ad_personalization and analytics_storage denied until you allow optional storage, and returns all four to denied when you decline or withdraw. The form remains available either way.

For Microsoft's handling of information, read the Microsoft privacy statement.

Read about storage choices