Inquiry collection
Unify scattered channels into a simple intake flow that your team can actually maintain.
Jinju and Gyeongnam inquiry automation
Website inquiry automation for Jinju and Gyeongnam businesses
Collect customer inquiries scattered across website forms, KakaoTalk, email, phone calls, and Naver TalkTalk. Save them to Google Sheets, Notion, or CRM, then connect AI summaries, staff alerts, quote drafts, and follow-up reminders.
Jinju academy consultations
Jinju clinic inquiries
Gyeongnam manufacturing quote requests
Local B2B lead tracking
When this is useful
Your website gets inquiries, but the follow-up flow is loose
The focus is not a prettier website. The core problem is what happens after a customer contacts you: capture, sorting, response, quote preparation, and follow-up tracking.
- Inquiries are split between a website form, KakaoTalk, phone calls, email, and Naver TalkTalk.
- Staff manually copy customer details into Google Sheets, Notion, or a CRM.
- Lead assignment and follow-up calls are delayed when the team gets busy.
- Manufacturing quote requests miss product names, quantities, drawings, or delivery dates.
- Academy consultations repeat the same level-test and schedule questions.
- Clinics answer the same reservation and visit-preparation questions manually.
Positioning
Inquiry operations before website decoration
Website production, AI, CRM, n8n, Make, Zapier, and SEO are treated as supporting tools. The main goal is to stop valuable inquiries from disappearing after they arrive.
Automatic storage
Save names, contacts, inquiry types, source channels, and requested services in one reliable place.
Consultation prep
Use AI to summarize long messages and classify the next action before staff reply.
Follow-up tracking
Track quote status, unanswered leads, reservation requests, and callback schedules.
Before / After
Demo flows by local business type
No invented performance numbers. These are practical automation patterns that can be adapted after reviewing your current inquiry flow.
| Business type | Before | After |
|---|---|---|
| Academy | Parent inquiries are handled one by one in messages and calls. | Student grade, subject, preferred time, and level-test request are stored before consultation. |
| Clinic | Reservation questions and preparation notices are repeated manually. | Inquiry type, preferred schedule, and visit notes are saved and routed to staff. |
| Manufacturing | Quote requests lack key information, requiring repeated follow-up. | Product, quantity, drawing link, deadline, and contact owner are captured before a quote draft. |
| Local B2B | Leads sit in inboxes and chat rooms without status tracking. | New, contacted, quote sent, and waiting statuses are tracked in a shared sheet or CRM. |
What can be automated
Only the steps needed to prevent missed inquiries
Automation starts from the smallest useful flow, then expands after the team confirms it fits daily operations.
Form to sheet or CRM
Send website form submissions to Google Sheets, Notion, Airtable, HubSpot, or an internal CRM.
AI inquiry summary
Summarize request details, urgency, missing information, and next actions.
Staff alerts
Notify the right person by email, Slack, Discord, or the tool your team already uses.
Quote draft prep
Organize quote conditions for manufacturing, B2B, consulting, or service inquiries.
Unanswered lead reminders
Create a practical reminder list based on status, date, and staff owner.
Source tracking
Record whether inquiries came from search, ads, Naver, referrals, or direct visits.
Connectable tools
Choose tools after defining the business result
KakaoTalk, Naver TalkTalk, and phone workflows depend on account permissions and available APIs. If direct integration is limited, the flow can start with staff input forms, email parsing, and shared records.
Inquiry channels
Website formKakaoTalkEmailPhoneNaver TalkTalk
Storage
Google SheetsNotionAirtableHubSpotInternal CRM
Alerts
EmailSlackDiscordKakao alert review
Automation engines
n8nMakeZapierCloudflare Functions
Workflow
Diagnose the inquiry flow first, then automate the smallest useful part
Check channelsForm, KakaoTalk, phone, email, Naver TalkTalk
Find leakage pointsStorage, owner, response delay, missing quote data
Design fieldsGoogle Sheets, Notion, CRM properties
Connect alertsAI summary, priority, staff notification
Add remindersQuote drafts, status checks, follow-up dates
Adjust after useRefine based on real inquiry patterns
Cost basis
Pricing depends on inquiry flow complexity
The cost is driven less by the number of web pages and more by the number of channels, records, owners, and follow-up steps that need to be connected.
| Complexity | Rough basis | Included flow |
|---|---|---|
| Basic inquiry cleanup | From KRW 1,000,000 | Website form, Google Sheets or Notion storage, email or Discord alert |
| Multi-channel inquiry flow | Around KRW 2,000,000-3,000,000 | KakaoTalk, email, phone memo, Naver TalkTalk flow review, CRM status setup |
| Quote and reminder automation | From KRW 3,000,000 | AI summary, quote draft, unanswered lead reminders, staff routing, operation test |
FAQ
Common questions
Do I need to rebuild my website?
No. If your existing form can be used, the first step is to connect storage, alerts, summaries, and follow-up tracking.
Can KakaoTalk or phone inquiries be automated?
It depends on account permissions and available integration options. When direct automation is limited, we start with realistic alternatives such as staff memo forms, email alerts, and shared records.
Is this only for Jinju?
The main focus is Jinju and Gyeongnam. Remote work for other regions can be discussed, but the service positioning and examples are designed for local businesses in this region.
Will AI reply directly to customers?
Not by default. The safer first step is AI-assisted summarization, classification, consultation prep, and quote draft support. Staff confirm important replies and prices.
Free diagnosis
Request a free inquiry flow diagnosis
Share where customer inquiries arrive and where follow-up gets missed. I will separate what should be automated first from what can wait.