Work a list of leads

1. Create the table from your CSV#

1. 1

   Create it

   In Tables, select New table, name it “Co-working leads, Plovdiv”, choose Import a CSV and Create table. The import opens on the new table.

2. 2

   Choose the file

   Choose file. Any size works; a file that isn’t UTF-8 text is refused before anything is sent.

3. 3

   Match the columns

   For each header choose the column it fills, a New column with its Type (Website as a link, Email as an email), or Don’t import. Under Merge rows with the same, keep Email, so the same lead imported twice stays one row.

4. 4

   Check and import

   Look over the first five rows and select Import 8 rows. The result lists rows added and merged, and every line left out with why (“Line 4, Email: Not an email address”).

2. Add a column an employee fills#

Enrichment columns fill each row with an employee’s work or a read from a connected app. Select Add column:

1. 1

   Name and type

   Name it “Opening line”, of type text.

2. 2

   Who fills it

   Choose An employee, then Elena. Under What to do for each row, write: “Write one friendly opening line for an email to {{Company}} in {{City}} offering our starter supplies bundle for co-working spaces. Plain text, at most 20 words.” Use a column inserts a column’s name.

3. 3

   Fill it

   Keep Fill all 8 rows after adding and select Add column and fill.

4. 4

   Set the batch

   Choose Only rows without a value, a Stop at budget and how many Calls at once, then Run on 8 rows.

A bar over the grid shows the batch: rows done, spent so far and about how long is left, with Pause, Raise budget and Stop. Select a cell to see who filled it, on which model, and what it cost.

3. Keep people off the list#

Before sending, open Do not contact from the table’s more actions. Add addresses or whole domains, one per line, with Why, and Add to the list. No table ever sends to them, and every send checks again.

4. Add the send column#

A send column writes once per row through a connected app, but only in batches you approve. Add column, and under Who fills it choose Sends:

1. 1

   Who and with what

   Employee: Elena (the send runs on her access). Connection: Gmail. Send with: Gmail’s send action.

2. 2

   What each email says

   Under Arguments, fill the recipient with {{Email}} and the message from {{Opening line}} and your own words.

3. 3

   Where it goes

   Contact address: the Email column, checked against the do-not-contact list before each send.

4. 4

   How many a day

   Sends a day: 30. Rows past it wait for the next day (UTC).

5. 5

   Which rows are ready

   Send only when: Status, with the ready value New, so leads you already contacted are left out.

5. Approve a batch#

From the send column’s menu choose Send rows. The sheet shows exactly what would go out:

• How many rows will be sent, and today’s sends against the daily limit.
• The rows left out and why: already sent, not to contact, not ready, missing a value.
• The exact rows: the first 50 listed with the address and every argument, the rest counted.

Set a Budget and select Approve and send 3 rows. If the table changed before your approval reached Royak, it is refused and shown again, so you never approve rows you didn’t see.

6. Daily capacity and bigger lists#

When a batch reaches Sends a day, its bar says today’s sends are used and when it goes on; it carries on by itself the next day. A batch holds up to 500 rows, so a longer list goes in several.

For lists you send every week, Give a standing approval for this column in the send sheet: a name and caps. Its first sends are a sample you confirm on the connection; after that, Send under it starts a batch with no row approval, until the column changes or it expires. Spikes of bounces or unsubscribes pause it by itself. See Standing approvals.

Questions#