Archive for July, 2010

Move All Events in a View – Torch Project Management

Thursday, July 22nd, 2010

Sometimes projects get behind/ahead of schedule. Now you can move all uncompleted events in a view by a specified number of days or weeks in Torch Project Management. First look at your filters:

You will only move events that match this view. So if you have a category selected, you will only move events in that category. If you have pinned selected, you will only move events you have pinned. Now click on "Move All Events":

For convenience, you are presented with a drop-down of weeks. However, you can also specify any arbitrary number of days:

Save Search to Category – Torch Project Management

Thursday, July 22nd, 2010

In Torch Project Management you can change the category on every item in a search result. Just perform a search for messages, event or Google Docs and Spreadsheets (you can use the same bucket selectors as before). Then select the category on the right or add a new category.

Torch Project Management Search – Detecting Intent

Sunday, July 18th, 2010

Torch Project Management has an amazingly powerful search system. With the use of bucket selectors you can drill down into your data and analyze every aspect of your project. However, bucket selectors are often confusing to new users.

Torch now tries to detect intent on simple searches (searches without bucket selectors or boolean operators). For instance, if you searched messages for:

train movement info@acme.com mark@acme.com

You probably intended to search e-mails between "info" and "mark" for the words "train" and "movement". So, Torch rewrites this search request as:

train movement email:info@acme.com email:mark@acme.com

Additionally, if you searched messages for:

pinned track planning

You probably intended to search pinned messages for "track planning". So, Torch rewrites this search as:

track planning pinned:yes

Let’s say you searched events for:

uncompleted pinned Mark James

You probably intended to search for an uncompleted event that you have pinned that mentions Mark James. So, torch rewrites this search as:

Mark James complete:no pinned:yes

Many more examples exist, but obviously this will never be as accurate as when you use the bucket selectors yourself.

You might also notice (at times) an optional notice that says:

Did you mean "X"

This happens when Torch is less sure what you intended.

Heap CRM Search – Detecting Intent

Friday, July 16th, 2010

Heap CRM has an amazingly powerful search system. With the use of bucket selectors you can drill down into your data and analyze every aspect of your business. However, bucket selectors are often confusing to new users.

Heap CRM now tries to detect intent on simple searches (searches without bucket selectors or boolean operators). For instance, if you searched messages for:

fireplace receipt info@acme.com mark@acme.com

You probably intended to search e-mails between "info" and "mark" for the words "fireplace" and "receipt". So, Heap rewrites this search request as:

fireplace receipt email:info@acme.com email:mark@acme.com

Additionally, if you searched messages for:

James Doe invoice 1234

You probably intended to search messages associated to "James Doe" for "invoice 1234". So, Heap rewrites this search as:

invoice 1234 association:James Doe

Let's say you searched prospects for:

(509) 000-0000 customer

You probably intended to search for a customer with a particular phone number. So, Heap rewrites this search as:

phone:(509) 000-0000 type:customer

Many more examples exist, but obviously this will never be as accurate as when you use the bucket selectors yourself.

You might also notice (at times) an optional notice that says:

Did you mean "X"

This happens when Heap is less sure what you intended.

Recommended Custom Values (Heap CRM)

Monday, July 12th, 2010

Heap CRM now displays the most recent custom values for a particular field in a information box to the left:

This is useful when a field should only have a few distinct values.

Search for Ranges in Custom Values (Heap CRM)

Saturday, July 10th, 2010

The Heap CRM "custom-value:" bucket selector now accepts greater than and less than operations. Let's say you have a custom value field called "Unrecoverable Cost" where you store costs associated with a transaction but are unchangeable. You could search for:

custom-value:Unrecoverable Cost>200

And find every prospect where the costs equal or exceed 200.

You can also search dates as well. If you had a custom value field named "Contract End Date" and you wanted to find every prospect who's contact ended this month you could search for:

custom-value:Contract End Date>7/1/2010 custom-value:Contract End Date<7/31/2010

Just as before, you can type in text, dates, and numbers in custom values. Heap does the work of detecting the type of data.

Remember, when you are searching prospects, you are searching prospect level custom values and when you are searching people you are searching people level custom values.

Create Time and Expenses with Torch Project Management WebHook

Monday, July 5th, 2010

You've always been able to create time and expense entries as part of a message sent through the Torch WebHook. But what if you want to create an expense or time entry without submitting a message? Now you can, here is some sample JSON:

{
"hours":"2:15",
"note":"Work with client",
"category":"Meetings",
"timestamp":"2010-07-04"
}

Or:

{
"price":"200",
"note":"New Widget",
"category":"Toys",
"timestamp":"2010-07-04"
}

Just like everything created via the WebHooks, this info can be posted as JSON or as POST fields. The only required fields are hours (for time), price (for expense) and note. Category and timestamp are optional.

Search Financial History (Heap CRM)

Friday, July 2nd, 2010

There is now nine new bucket selectors for Heap CRM's ever expanding search system:

history-type:lead|opportunity

Limits history records to leads and opportunities.

history-before: -5 weeks history-after: -4 weeks

Limits history records to between four and five weeks ago.

history-expected-value-greater-than: 500 history-expected-value-less-than: 2000

Limits search to history records with an expected value between (and including) $500 and $2000.

history-probability-greater-than: .25 history-probability-less-than: .7

Limits search to history records with a probability of success between (and including) 25 and 70 percent.

history-value-greater-than: 2000 history-value-less-than: 10000

Limits search to history records with a potential value between (and including) $2000 and $10,000.

Obviously, these are best used used together. For instance, let's say I want to find all customers created between June 20th and June 25th with an expected value greater than $200:

history-after: 6/20/2010 history-before: 6/25/2010 history-type:customer history-expected-value-greater-than: 200

Note: Starting on June 10th, 2010 Heap CRM started to store a history of when a prospect was converted from one type to another, the value was changed or the probability was changed. This is the second feature to use this data.