Reach out.
A short message gets a real response. No calendar widgets, no AI-generated reply chains, no drip sequence. Use the form or write to us directly — both reach the same person. We read every message; we answer within one business day.
Tell us what you need.
Everything here lands in the same place as an email would. If you'd rather write directly, the addresses are below.
Or email directly, by topic.
botfather@coreshift.technology
The right starting point for most conversations: "could a bot fit this workflow," "what's the pilot program like," "when will [bot name] be ready." Use the form above and include a paragraph about your business and what you're hoping to offload.
security@coreshift.technology
For responsible disclosure of security issues. Use the form above with "Security disclosure" as the topic. We acknowledge within 24 hours and provide a disposition within 72 hours. See our security reporting policy.
support@coreshift.technology
Existing pilot or paying customers — issues with a running bot, configuration questions, data export requests, billing. Submitted messages are monitored during business hours; urgent issues are escalated via the Telegram operator channel set up during onboarding.
botfather@coreshift.technology
Press inquiries, integration partnership conversations, or other business development topics. Use the form above with a clear note on the topic.
If you're writing about a pilot or fit question.
The fastest path to a useful response is including these details up front:
- What your business does — one sentence is fine. "We're a 12-person electrical contracting firm in San Diego."
- The workflow you're hoping to offload — be specific. "Bid coordination — we do 8-12 bids/month and chasing vendors is killing us." Not: "We need AI."
- What tools you already use — Outlook or Google Workspace, your CRM (if any), your accounting (QBO/Xero/etc), your SMS provider (if any). Helps us tell you fast if we already integrate.
- Your timeline — "exploring now" vs "need something live by Q3" changes the conversation.
- How you found us — helps us understand which audiences our communication is reaching.
A 5-sentence email with the above information gets a real, considered response within one business day. A one-line "interested in your product" gets a polite but generic reply.
How a typical conversation goes.
-
Initial email exchange.
You write a paragraph. We reply with whether one of our bots fits your workflow, what the realistic timeline is to onboard, and what onboarding would involve. If it's not a fit, we say so plainly.
-
30-minute call (if there's a fit).
We learn more about your operation, you ask more about how the bot works. Calls are screen-share-friendly so we can walk through what your bot would do specifically for your business. Recorded only with your permission.
-
Proposal or pilot scoping.
If we both want to proceed, we put together a written proposal — bot, scope, configuration, integrations, timeline, pricing. For pilot customers, this includes the 30-day pilot terms. See pilot program details.
-
Onboarding (typically 1 week to first real usage).
We configure your tenant, set up integrations together, import your data, run 2-3 dry-run workflows with you watching, then turn on live mode. Direct contact with the engineer building your bot throughout.
For physical mail.
CoreShift Technologies LLC
San Diego County, California
Full mailing address provided after pilot scoping or contract signature.
We do not publish a public mailing address. Pilot customers and contracted parties receive the address as part of the engagement. Press inquiries can request the address via email.