Contact JumpsuitAI Support and Sales

Reach out to contact JumpsuitAI for plugin support contact, sales inquiries, or feature requests. Were here to help you automate llms.txt and Markdown generation with a privacyfirst approach. Before writing in, you may find instant answers in our FAQs or a quick overview of capabilities on the Features and Pricing pages.

Illustration showing WordPress, messaging icons, and a support inbox representing JumpsuitAI contact and support

Get support or sales answers

Cards representing technical support, sales inquiries, and feature requests for JumpsuitAI
  • Technical support: Troubleshooting, setup guidance, and usage tips.
  • Sales inquiries: Licensing, renewals, and plan questions.
  • Feature requests: Ideas to improve workflows or content organization.

Tip: For the fastest help, include your WordPress version, the JumpsuitAI Pro version, relevant URLs, and steps to reproduce issues.

What to include in your message

Provide details that reduce backandforth and speed resolution:

  • Your WordPress version, theme, hosting environment, and PHP version.
  • JumpsuitAI Pro version and any recent updates applied.
  • A short problem description, the expected outcome, and what you’ve tried.
  • Screenshots or non-sensitive logs showing errors or unexpected behavior.
  • The URL of the affected page or post, if applicable.
  • Your preferred contact method and time zone for follow-ups.
Checklist showing required details for JumpsuitAI support messages, including versions, steps to reproduce, and URLs

How to reach the right team

Diagram showing how messages are routed to technical support, sales, or feature request teams for JumpsuitAI

Technical support

Describe the issue clearly and share any error messages or logs if available. Mention your site URL and recent changes (themes, plugins, or updates) to streamline technical support. If the problem is intermittent, note the frequency and any patterns you notice.

Sales inquiries

Unsure which plan fits your needs, or how licensing works across sites? Review the Pricing page, then send your questions so we can point you to the most efficient option for your workflow. If you’re comparing solutions, the Comparison page may provide helpful context.

Feature requests

Suggest enhancements that would make your content mapping and llms.txt workflows easier. Prioritize what matters most; we track feature requests and evaluate them alongside roadmap goals. Include a short use case, desired outcome, and any examples that illustrate your idea.

Response times and availability

We aim to reply as quickly as possible during typical business hours. Exact response times are not specified in the current materials; if you have a timesensitive matter, note your deadline so we can prioritize appropriately. Complex questions or issues that require reproduction may take longer; we’ll acknowledge receipt and keep you updated as we investigate.

Illustration showing support response timing with a weekly schedule and inbox status indicators such as acknowledged and in progress
Illustration emphasizing privacy and secure data handling, showing a document with redacted content, a shield icon, and a warning indicating no passwords should be shared

Data handling and privacy

Please avoid sharing passwords, access tokens, or other sensitive credentials in your initial message. When sensitive details are required to proceed, we will outline secure, leastprivilege options for sharing them. Where possible, provide redacted logs or screenshots that exclude personal data. Our guidance is privacyfirst, and we focus on the minimum information needed to help.

Selfserve resources

Many common questions are covered in our documentation and posts. Start with:

  • FAQs for quick answers and known solutions.
  • Features for capabilities, supported workflows, and limitations.
  • How-to for step-by-step guidance on typical tasks.
  • Pricing for plans, renewals, and licensing notes.
  • Blog for tips, updates, and best practices.
Illustration showing a list of self-serve help resources including FAQs, Features, How-to guides, Pricing, and Blog content
Illustration showing the support process flow after submission: confirmation, checklist follow-up, and resolution summary

After you submit

You’ll receive a confirmation that your message was received. If we need more details, we’ll reply with a short checklist so you can provide the most helpful information in one go. For ongoing threads, please reply within the same conversation to preserve context, and include any new steps you tried since our last message. Once resolved, we’ll summarize the fix so you have a clear reference for the future.

Send your message

Fill out the form and send us a message.

    FAQs

    How do I get technical support?

    Share a concise description, your site URL, environment details, and steps to reproduce the issue. Check FAQs first for known answers.

    We aim to respond as quickly as possible, please indicate urgency and we will respond as quickly as possible. Make note that all licensing and payment questions should be directed to Freemius the license provider.

    Send your feature requests here with clear goals and examples. Reviewing the Features page first helps avoid duplicates.

    No, we do not offer phone support at this time. Please direct all payment and licensing requests to the license provider Freemius. For all other queries fill out the form above.

    Need a quick overview? Visit Home to see how JumpsuitAI prepares your site for AI search engines.