> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# What Is the Best Way to Track Internal Requests Between Sales and Production?
- URL: https://blog.jestor.com/internal-requests-sales-production/
- Published: 2026-10-13T21:20:18.000Z
- Updated: 2026-10-13T21:20:18.000Z
- Author: Bruno Bannach

A clear way to **track internal requests between sales and production** is to replace hallway conversations with a simple request board: each request has a type, a requester, an owner in production and a response deadline, and the answer is recorded on the card.

In **Jestor**, requests such as date checks, feasibility questions and priority changes move through a **Kanban** with **SLA** tracking.

## Why do sales and production clash?

Sales asks production for delivery dates, technical answers and urgent priorities, often by walking to the floor or calling.

Production is interrupted constantly, answers are forgotten and sales gives customers information that is not confirmed.

Tension grows between the two teams.

## What problems does a request board solve?

- Constant interruptions on the shop floor
- Answers given verbally and forgotten
- Unconfirmed dates promised to customers
- Priority changes without agreement
- No record of what was requested

## How do I set up sales-to-production requests in Jestor?

1. **Create a request form** with type, order, customer and question.
2. **Define types**: Date check, Feasibility, Priority change, Sample, Technical question.
3. **Assign owners** in production by type.
4. **Set SLA deadlines** for answers.
5. **Record answers** on the card for sales to use.

| Request type       | Owner              |
| ------------------ | ------------------ |
| Date check         | Production planner |
| Feasibility        | Engineering        |
| Priority change    | Production manager |
| Technical question | Engineering        |

## How do I handle urgent priority changes?

Priority changes affect other orders, so they should be approved by the production manager.

Recording the decision avoids disputes when another customer's order is delayed.

## Why use Jestor for sales-production requests?

- **One channel**: every request recorded.
- **SLA tracking**: response times visible.
- **Recorded answers**: sales uses confirmed information.
- **Internal chat**: mentions on cards replace side conversations.

## What else helps you track internal requests between sales and production?

- Request data also reveals patterns. Many date checks may indicate that sales needs direct access to the production board.
- Production can also proactively publish updates. Sharing expected completion dates on the production board answers many questions before sales needs to ask.
- This reduces requests and builds trust between the teams.
- Requests that repeat often can become standard answers or shared views, freeing production from routine questions.

This is how you track internal requests between sales and production and reduce friction.

## Frequently Asked Questions

### Can requests be created from a phone?

Yes. The request form works on mobile.

### Can I try it free?

Yes. Create a free account at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### Can I measure response times?

Yes. SLA tracking records time per phase.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**.

Discover Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.