SUPPORT
Help with work
already in motion.
For an existing Batisha Labs engagement, a purchased digital product, or a question about a currently available verified product. Find the right path and bring enough safe context to begin.
01 / CHOOSE YOUR SUPPORT PATH
Choose by the issue in front of you. Something new to build belongs in project intake.
01 / EXISTING ENGAGEMENT
Use the communication path already agreed for your Batisha Labs engagement. It preserves history, decisions and ownership. If that path is unavailable or inaccessible, email Support.
Email Support as a fallback02 / DIGITAL PRODUCT
For a purchased product or a question about a currently available verified Batisha Labs product: supplied files, included material, instructions, usage or reasonable compatibility clarification.
Email Support about a product03 / SECURITY CONCERN
For a suspected vulnerability, unauthorized access, credential compromise or possible data exposure. Do not send secrets or compromised credentials through ordinary support email.
Security guidance04 / NEW PROJECT
For new systems, workflows, integrations, automation, AI capability, redesign or substantial expansion. Customizing or implementing a product for your business may become new project scope.
Start a ProjectGeneral business correspondence? General Contact
02 / PRODUCT OR PLATFORM?
Batisha Labs product questions and storefront-controlled problems have different starting points.
Incorrect or damaged supplied file, missing included material, content questions, instructions or usage clarification: contact Batisha Labs Support.
Use the product name and the relevant file or instruction. A purchase does not imply custom setup, free implementation, universal compatibility, lifetime support or guaranteed updates. Check the listing for its boundaries.
Digital ProductsFor payment, checkout, storefront-account, receipt or platform-controlled download and delivery problems, begin with the storefront used for the purchase.
Official channels include Payhip, Gumroad and Ko-fi. Availability, transaction processes and policies may differ. Use your purchase’s platform and its guidance; for an issue with the Batisha Labs product itself, contact Support.
Review the relevant storefront listing and transaction terms. Website terms →
03 / A USEFUL FIRST MESSAGE
Use the questions that help explain your issue. You do not need to answer every one or collect every detail.
Name the project, product, page, workflow, system or step.
Describe the intended result without guessing the cause.
Share the observable behavior, error or missing result.
Include approximate timing, relevant changes or the last known working condition.
Share useful actions already taken so work is not repeated.
Explain the work or decision that cannot continue and its practical consequence.
A public URL, product or system name, browser, device type, operating-system or non-sensitive version number, approximate timestamp, error text with secrets removed, general reproduction steps or a sanitized screenshot. Keep unrelated material out.
04 / SECURITY + PRIVACY BOUNDARY
Ordinary support email is not a secure file-transfer channel. Start with a high-level, non-sensitive description. If sensitive material is needed, agree an appropriate secure method first.
05 / CONTEXT + OWNERSHIP
A request may move to the correct owner or route without losing useful context. Keep one current owner and the next action clear. Sending a message alone does not confirm resolution or accepted ownership.
Keep decisions, approvals, previous attempts, constraints, current owners and open questions connected. Sensitive material stays within its approved communication boundary. If you need the fallback email, summarize the current condition and business consequence; do not recreate the entire project history.
How engagements workEscalation means the current owner, route, permission or technical capability is no longer sufficient. Delivery blockers, scope changes, sensitive commercial, contract, security, privacy or relationship decisions, conflicting evidence and exceptions may need another authorized owner. It does not promise urgency or an automatic executive handoff.
For missing context, duplicate requests, access failure or a failed handoff, retain the known condition, safe evidence, reason the route failed and open decision. Clarify only what is missing, make dependencies and the next action explicit, identify the responsible next party, confirm accepted ownership and verify the result or explicit next action.
06 / BEGIN WITH THE USEFUL DETAIL
Include the relevant project or product, expected result, observed result, current impact and safe supporting context. For active engagements, use the agreed path first.
support@batishalabs.com