customer-db

Manages persistent customer records and follow-up tasks in a SQLite database.

8.4k|1.4k|Updated Apr 24, 2024
One-click install
npx skills add https://github.com/TeamWiseFlow/wiseflow --skill customer-db
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: customer-db
Source: https://github.com/TeamWiseFlow/wiseflow/tree/main/addons/officials/crew/sales-cs/skills/customer-db
Command: npx skills add https://github.com/TeamWiseFlow/wiseflow --skill customer-db

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the problem of losing customer context between sales-cs sessions by persisting customer records and follow-up status in a local SQLite database.

Core Features & Use Cases

  • Persistent customer records: Maintains a per-peer SQLite database at ./db/customer.db with a stable schema (cs_record, primary key peer).
  • Controlled field updates: Provides a safe update path to set purpose and prompt_source while always bumping updated_at, without overwriting with empty values.
  • Follow-up task lifecycle: Creates, cancels, queries due tasks, expires stale tasks, and marks send/complete transitions (pending → sent_once → completed).

Use case: When a sales-cs workflow invites a lead and then needs delayed nudges, customer-db stores business_status handled by hooks, updates narrative fields when new info arrives, and schedules/executes follow-up messaging with clear state transitions.

Quick Start

Tell the AI to update the current customer’s purpose and prompt_source using the cs-update script, providing the peer from CustomerDB and the new values when you have clearer information.

Frequently Asked Questions about customer-db

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate sales follow-ups while keeping customer context across sessions?

Automating sales follow-ups while keeping customer context across sessions requires a persistent SQLite database to store customer records and track follow-up task states like pending, sent_once, and completed. This approach ensures no context is lost between interactions.

What is the best way to manage lead progression in a local customer database?

Managing lead progression in a local customer database involves using a state machine to handle business_status transitions and follow-up task lifecycles. Peer-based database operations ensure records are safely updated without overwriting existing narrative fields with empty values.

How do I query expiring follow-up tasks inside my sales workflows?

Querying expiring follow-up tasks inside sales workflows is done by executing scripts against the local customer database to find due or stale records. The system expires stale tasks and marks send or complete transitions based on the follow-up lifecycle state.

Does SQLite work for tracking customer engagement context in a sales-cs workspace?

SQLite works for tracking customer engagement context in a sales-cs workspace by maintaining a per-peer database with a stable schema. It safely handles controlled field updates for purpose and prompt_source while delegating business_status changes to system hooks.

Can I overwrite customer fields with empty values when updating a lead database?

You cannot overwrite customer fields with empty values when updating a lead database because the update path enforces safe non-empty updates for purpose and prompt_source. The system always bumps the updated_at timestamp to maintain data integrity.

When should I use a state machine for lead management follow-up automation?

You should use a state machine for lead management follow-up automation when a sales-cs workflow needs delayed nudges after inviting a lead. It schedules and executes follow-up messaging with clear state transitions from pending to sent_once to completed.