This repository holds the default community health files and shared engineering templates for every public TextConvo repository.
GitHub applies the files below automatically to any TextConvo repository that does not define its own version.
| File | Applies to | Purpose |
|---|---|---|
| CONTRIBUTING.md | All public repos | How to propose changes, branch, commit, and open a pull request. |
| CODE_OF_CONDUCT.md | All public repos | Expected behaviour in issues, pull requests, and discussions. |
| SECURITY.md | All public repos | Coordinated vulnerability disclosure process. |
| SUPPORT.md | All public repos | Where to get help. |
| CODEOWNERS | This repo | Default review ownership template. |
| .github/PULL_REQUEST_TEMPLATE.md | All public repos | Pull request checklist. |
| .github/ISSUE_TEMPLATE | All public repos | Bug, feature, documentation, and example-request forms. |
| Template | Use it for |
|---|---|
| templates/README_TEMPLATE.md | Starting a new public repository with a consistent README. |
| templates/RELEASE_TEMPLATE.md | Writing GitHub release notes. |
| templates/labels.yml | The standard label set applied to every public repository. |
| templates/REPOSITORY_STANDARDS.md | Descriptions, topics, discussion categories, and branch conventions. |
TextConvo product code is private. Public repositories contain examples, specifications, SDK surfaces, and documentation only — never platform implementation, orchestration logic, infrastructure, or credentials.
Reference documentation is not duplicated here. textconvo.ai/docs is the single source of truth; this account is the public engineering landing page.
Website · Developer Docs · API Reference · Webhooks · Blog · LinkedIn · Contact
Submit the contact form and you get a direct line to Ria, the TextConvo AI orchestrator — call her for a live voice demo, or text her and watch the SMS AI reply in real time. A human follows up within one business day, and the same form is how API credentials, a source key, and a webhook secret are issued.
Handed a TextConvo QR code at an event or in a demo? Scanning it opens the same conversation. The form is simply the path that works for everyone.