Slash: why business banking is moving to messages
Blog post from Linq
Slash shifted from serving sneaker resellers with virtual cards to providing business banking for SMBs and mid-market companies after the sneaker resale market declined, and it now processes more than $1 billion in monthly transaction volume. Its next strategy centers on using iMessage as a primary interface for field employees, contractors, and other cardholders who rarely use banking dashboards but need simple ways to submit expenses, deposit checks, check budgets, and request reimbursements. By combining threaded messaging with AI agents and banking-system integrations, Slash aims to turn messages into actionable workflows rather than one-way notifications, while retaining dashboards for more complex tasks such as disputes and card configuration. The approach relies on fast response times, strong authorization controls, encrypted and compliant messaging infrastructure, and careful design that avoids forcing users between text and app-based workflows. Slash argues that advances in AI agents and modern iMessage APIs make this model more practical in 2026 than earlier SMS-based banking experiences, though it emphasizes presenting the service as texting a bank rather than using an AI assistant.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| AI Agents | 1 | 5,422 | 1,164 | 237 | -21% |
| AI Coding Assistant | 1 | 1,400 | 436 | 132 | -25% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.