Skip to content
KynectLocal Docs

Feature Requests

Submit a feature request by emailing the KynectLocal product team — this page explains what to include and what happens after you send it.

When you’d use this

Section titled “When you’d use this”
  • You have a workflow that KynectLocal does not currently support and want to suggest it
  • You want to propose an improvement to an existing feature
  • You’re a developer who needs a new API endpoint or webhook event

How to submit a request

Section titled “How to submit a request”

You can send a request from any role — brand admin, location operator, or developer. There is no form to fill out. A short, clear email is all that’s needed.

What to include

Section titled “What to include”

A useful request answers these questions:

  1. What are you trying to accomplish? Describe the goal, not just the solution. “I need to notify franchisees when a template is updated” is more useful than “add a notification button.”
  2. What is your current workaround? If you have one, describe it — this helps the team understand urgency and the cost of the gap.
  3. How many users or locations would benefit? Give a rough sense of scope. Network-wide impact carries more weight.
  4. Which role does this affect? Brand admin, location operator, or developer.
  5. Relevant screenshots or links. If the request relates to a specific page in the admin, include the URL.

Review process

Section titled “Review process”
StageWhat happens
ReceivedYour request is logged and acknowledged within 2 business days
Under reviewThe product team evaluates feasibility, frequency, and fit with the roadmap
Roadmap decisionAccepted requests are added to a future release; declined requests receive a brief explanation
ShippedThe feature appears in What’s New and Changelog

Review does not guarantee implementation. Requests that align with a common use case or affect multiple brands are prioritized over one-off needs.

Section titled “Related”