Skip to main content

Konnie in Apps

Konnie can help with the App you are using from the regular chat or side drawer. A custom React App can also provide its own text, recorded-voice or attachment controls. The App owns the interaction and available actions; it does not need a separate embedded assistant or Form component.

Work with the current App​

  1. Open an assigned published App and verify its workplace, selected record and task.
  2. Open Konnie and state the outcome you want. Name the App or exact record if context could be ambiguous.
  3. Supply the source, photo or other evidence needed for the question and wait for upload completion.
  4. Review proposed input changes and preserve unrelated answers.
  5. Submit or perform the authorized action only when it is intended, then inspect the actual saved result.

Example: “Use this photo to suggest a description for the visible surface defect in the current inspection App. Leave the acceptance decision for me and preserve the other answers.” A generated description is a suggestion, not a physical observation or quality approval.

What Konnie can see and do​

An App can expose the selected task, readable context and named actions. For example, it can allow Konnie to read a draft, fill selected values and invoke the same submission handler as the App's button. The App author determines the contract. Opening the drawer does not automatically expose every input or grant access to every factory record.

Check any displayed target and result. Current account, published App bindings, workplace and native business rules still limit reads and writes. Autonomy and required reviews apply. Ask explicitly for a draft or analysis when no operational change is intended.

Configure a useful interaction​

As an author, ask Konnie to expose only the current task and actions that help the person finish it. Name source fields and destination records, preserve other draft values and define when submission is available. Use ordinary App settings for useful editable options and ordinary source for layout, conditions and validation.

A production App might expose its selected position and a progress action. A request App might expose patchDraft and submitRequest. Use the App interaction and operational SDK rather than copying platform records into an ungoverned store.

Existing component-based Apps may retain their embedded Konnie configuration and conversation. Follow that App's visible controls for related follow-up; do not assume an old embedded conversation is automatically the same as the current main chat. New custom Apps can implement the whole task directly.

Verify and recover​

Test English/German, desktop/narrow, intended-user and denied-user states. Check context changes, missing selection, attachments, draft changes, explicit submit and its destination after reload. Compilation does not prove those runtime results.

If the context is wrong, stop and select the right record before continuing. If an action times out, preserve its original request and inspect the destination before retrying. Voice/Live availability depends on the device and configured provider. See data entry, building Apps and support.

Talk while working​

  1. Open an assigned App and check its selected order or task.
  2. Select Talk to Konnie and allow microphone access. Wait for the listening state.
  3. Ask a question or request an action: “Read the latest order status,” “Record this measurement,” or “Change the quantity to three.” Available operations depend on the App.
  4. Listen to the result and check the updated workspace. Konnie distinguishes a prepared draft from a saved or submitted record.

You can interrupt a spoken answer and correct earlier input in the same conversation. Minimize the panel to keep working; microphone and end controls remain visible. Mute stops sending microphone audio. End stops audio; already accepted work may still finish. Stop current task, or an explicit spoken request such as “Stop that task,” requests cancellation of current work. Saved changes remain.

Use Type or view history to switch to text without losing an unfinished message. Switching Apps or orders pauses the bound spoken session. Check the new target and start talking again. Automatic shop-floor playlist rotation pauses while the companion is active or its work remains pending.

Live requires an enabled and approved speech connection, a supported browser and microphone access. If unavailable, you can use text and the ordinary App controls. See Voice and Live.