Something broken, something confusing, or something you need changed. Tell us what is happening and we pick it up — you are not filing into a queue nobody reads.
Same day
Response target when a live site or application is down
1 day
Response target for everything else, including questions
60 days
Post-launch support included with every build, at no cost
No tiers
Your request reaches the people who built the thing you are asking about
Use this form to contact our agency.
No ticket numbers, no first-line script, no being asked to restart your browser. Four steps, and a human reads step one.
Step 01
What you were doing, what you expected, and what happened instead. A screenshot or a link to the page saves us an entire round trip.
Step 02
Before touching anything we confirm the behaviour ourselves, so the fix addresses the actual cause rather than the symptom you happened to notice.
Step 03
A plain description of the cause, whether it falls under your plan, and what it would cost if it does not. You decide before anything is billed.
Step 04
The change ships and we tell you when it is live, rather than leaving you to check. Anything structural gets written down for the next person.
All three reach the same inbox. Naming it just helps us open the right thing first.
Something is broken
A page will not load, a form stopped sending, an integration is failing. Include the URL and roughly when it started and we can usually find it fast.
Report a problemAccount and billing
Questions about an invoice, changing a hosting plan, adding or removing team members, or transferring ownership of a project to someone else.
Ask about your accountChanges and new work
Content edits, new pages, new features. Small changes are often already covered by your plan; anything larger gets a quick estimate before we start.
Request a changeA support request is not an interruption of the work — it is the work. The people who built your site are the ones who answer it, which is exactly why we keep the client list small enough to do that properly.
Iain Feeney
Founder, Stacklumen
If you are on a hosting or maintenance plan, most of this is already included. If you are not sure, ask — we would rather tell you it is free than let it sit broken.
If something we host goes down, that is ours to fix. There is never a charge to have an outage looked at, whatever turns out to have caused it.
Dependency updates, platform changes and security patches are applied as part of hosting rather than billed to you as separate pieces of work.
Copy changes, image swaps and small layout fixes on hosted sites. Send them in plain language — you do not need to write a formal ticket.
Form delivery, analytics, payment and CRM connections. These tend to break quietly, so tell us the moment something looks off rather than waiting.
Slow pages, failing Core Web Vitals and broken metadata are investigated as part of ongoing maintenance, not treated as a separate engagement.
Lost a password, adding a teammate, moving a domain. We would rather help you into your own accounts than sit in the middle of them.
The things people ask before they write in. If yours is not here, ask it in the form above.
Email support@stacklumen.com with “urgent” in the subject line, or use the form above. If a site we host is fully down, we aim to respond the same day.
Every build includes 60 days of post-launch support. After that, hosted clients get maintenance and small edits as part of the plan; larger work is quoted first.
Text changes, image swaps, or adding a page from a template you already have. If it takes us under roughly half an hour, it is generally covered without a quote.
Sometimes. We start with a paid audit so we understand the codebase before agreeing to maintain it, and we will say no if it cannot be supported responsibly.
In the client portal at stacklumen.com/app. If you cannot get in, email support and we will send them across directly while we sort the access out.
Yes. Call 901-390-6259 during business hours, or ask in your reply and we will arrange a call. Complicated issues are usually faster to explain out loud.
Send it over even if you cannot describe it properly. A vague report is far better than a silent one.